BlueSaab v4.1 released!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

BlueSaab v4.1 released!

Seth
Administrator
This post was updated on .
Version 4.0 was a test case; it works but needed a few small tweaks, so hence it wasn't released.

Version 4.1 has the following changes:
- All SMD parts! (except for FTDI 6-pin, ISP header, and reset pins).
- Incorporates built-in FTDI interface, so now uploading code is as simple as plugging in a mini USB cable!
-- If you have an FTDI cable/adapter, you don't need to populate the on-board FTDI components, just use the 6 pin FTDI header to program like previous versions.
- Changed from a hard to find voltage regulator to a MUCH more common 3.3v regulator.
- No software changes are required; uses exact same code as previous hardware version.

OSHPark BlueSaab 4.1 Link

Mouser BOM

There will be an extra step to get this module to work. Most likely the 328 will not have a bootloader, so you will need to burn the bootloader first, using the ISP header and another Arduino. After that's been accomplished, upload code like normal.
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Trionic Seven
I've just built the 3.3 and you surprise me with this ! :)

Great work, a big round of applause to the developers!
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Seth
Administrator
sorry about that...but you're really not missing much. v3.3a is the most popular version (so far...) :)
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Karlis
Administrator
Continuous improvements are always a good thing. We try to keep the upgrades as painless as possible. :)
2001 9-5 SE V6; 2006 9-5 Wagon; iOS; BlueSaab version = "latest and greatest" :)
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

homerisback
Great work guys !
I saw the v4.0 at OSHPark website and was waiting for an official launch here with champaign
I still have my two extra modules, build and ready to plug'n play but french fellowes remain using those parrot things or hesitating despite my enthusiast feedback...
Keepin' on following any code improvement, especially about SID.
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Karlis
Administrator
Just out of curiosity - what are those Parrot alternatives that are being used?
2001 9-5 SE V6; 2006 9-5 Wagon; iOS; BlueSaab version = "latest and greatest" :)
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

NPen
In reply to this post by Seth
Hey,

I have a 9-5 my06 with denso nav2. Also have bluetooth Nokia ck-7w , which is using the soundspeekers and mic of the car. Is this will be e problem? How will work the car kit and the bluesaab if they both active? I want to have one of this. Is there a way to send me only 1 pcb via your national post? Of course i will pay for it.

Regards,
Nik
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Seth
Administrator
I don't think this module will work in your model year...afaik, it will only work in 1999-2005 9-5's...

but if you find out I'm wrong, I have a blank v3.3a or v3.2 pcb I could send you.
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

NPen
That is the main difference? Later today i will give a photo of my ch changer and head unit. Also the cable connected to the cd changer. Is this made before? I mean with 9-5 2006 with denso satnav?
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

viv.g
In reply to this post by Seth
Seth wrote
There will be an extra step to get this module to work. Most likely the 328 will not have a bootloader, so you will need to burn the bootloader first, using the ISP header and another Arduino. After that's been accomplished, upload code like normal.
Hey guys,

Just wondering if you have any more information on how to do this? I have an arduino and the board fully built, but not sure how to upload the bootloader whilst its on the board...

Any clues? :) or a relevant link?

Cheers,

Viv
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

viv.g
viv.g wrote
Seth wrote
There will be an extra step to get this module to work. Most likely the 328 will not have a bootloader, so you will need to burn the bootloader first, using the ISP header and another Arduino. After that's been accomplished, upload code like normal.
Hey guys,

Just wondering if you have any more information on how to do this? I have an arduino and the board fully built, but not sure how to upload the bootloader whilst its on the board...

Any clues? :) or a relevant link?

Cheers,

Viv

Think I may have it... installing an arduino bootloader/connecting the programmer
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Seth
Administrator
Yeah, that tutorial should be helpful. The way I do it is to install the ArduinoISP sketch to my Arduino Uno, (I use a shield then, on top of the Uno that gives me a 2x3 and a 2x5 header that I can use to connect an ISP cable from the shield to the BlueSaab ISP header; but all this is just for ease; it's not required), then I connect the Uno to the bluesaab at the ISP header, then in Arduino IDE I select Arduino Uno as the board, select the correct com port, CHANGE THE PROGRAMMER TO "ARDUINO AS ISP", and then Tools, Burn Bootloader.

So in this process, we send an Arduino Uno's bootloader to the bluesaab chip so it acts just like a regular Arduino Uno. This allows us to easily upload code via the FTDI header or USB upload plug.
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Hello,
sorry for repeating question, I just finished my first 4.1 board and I tried upload SW or burn bootloader through USB cable with pc and Andruino IDE, boths not working (no response from procesor) .
So I must use second andruino board  to burn  bootloader  through ISP ? or there is other way ?

Thanks for answer Petr W



 
 
SAAB 9-5 Aero 2002
BlueSaab 4.1
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Seth
Administrator
Yes, you have to burn a bootloader to the 328 chip before you can upload any code. This is done via the ISP pins on the BlueSaab board. I've found the easiest way is to use an Arduino Uno (you can use any Arduino board, or any ISP programmer) to do this. Burning the bootloader to the BlueSaab 328 is a one-time process; you shouldn't ever have to do it again. Once it's on there, it never goes away (unless some sort of catastrophic event happens; ESD, etc).
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Thank you Seth ! 
SAAB 9-5 Aero 2002
BlueSaab 4.1
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

saab95
In reply to this post by Seth
What are the main difference between version 4.1 and 5.0?
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Seth
Administrator
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

Karlis
Administrator
In reply to this post by saab95
In a nutshell, the main differences between v4.x and v5.0 of BlueSaab -> v5.0 has:

   - smaller components (to save space on the PCB)
   - DFU switch is gone (now diodes take care of the task)
   - additional caps/resistors to make signals "smoother"
   - 10-pin connector for an optional AMP shield
2001 9-5 SE V6; 2006 9-5 Wagon; iOS; BlueSaab version = "latest and greatest" :)
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

saab95
:-)
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Hello All!
I´m  the beginer and now trying burn bootloader to my Bluesaab 4.1.  through Arduino uno clone.
I used some base tutorial  ISP sketch / arduino as ISP and then burn bootloader.

But happend this error: Device signature = 0xffffff (probably .reduced_core_tiny) (retrying)


Can somebody help me what is wrong_? if this can be hardware soldering problem or I must something setup in sketch? (SPI clock)  

Thanks and regards Petr W

https://photos.google.com/share/AF1QipMg90jMagF79KgNqo3OF0S0d63qwLwT9z0DhJy4hw8zuqwrVlYm0n7w9H85YQetgA?key=SnU0TFJwcm1odnF2ZWFYOU9iOExYYU82MmJIZk13

Eror mesage from IDE:
Arduino: 1.6.13 (Windows 7), Board: "Arduino/Genuino Uno"

C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -cstk500v1 -PCOM5 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0x05:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m

avrdude: Version 6.3, compiled on Sep 12 2016 at 17:24:16
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : stk500v1
         Overriding Baud Rate          : 19200
         AVR Part                      : ATmega328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500
         Description     : Atmel STK500 Version 1.x firmware
         Hardware Version: 2
         Firmware Version: 1.18
         Topcard         : Unknown
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0xffffff (probably .reduced_core_tiny) (retrying)

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0xffffff (probably .reduced_core_tiny) (retrying)

Error while burning bootloader.
Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0xffffff (probably .reduced_core_tiny)
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.


avrdude done.  Thank you.
SAAB 9-5 Aero 2002
BlueSaab 4.1
12