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
|

Re: BlueSaab v4.1 released!

Seth
Administrator
Your cap is going to the reset pin on your uno. I think it actually is supposed to go to the reset "line" from uno to BlueSaab (pin 13? Can't remember which pin is used as reset). Give that a try.

On Thu, Nov 24, 2016 at 13:58 PetrW [via BlueSaab Forum] <[hidden email]> wrote:
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



If you reply to this email, your message will be added to the discussion below:
To start a new topic under Hardware, email [hidden email]
To unsubscribe from Hardware, click here.
NAML
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
I tried reconect reset directly or disconect reset and happend little diferent error:

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.

I found this:

http://www.avrfreaks.net/forum/does-device-signature-0x000000-mean-atmega-bad

looks that its some trouble with crystal
SAAB 9-5 Aero 2002
BlueSaab 4.1
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

viv.g
Hey mate,

Encountered a few similar issues when going through the process.

In the end, it turned out it was a faulty solder connection somewhere. I went through and checked all connections and reheated them to ensure a proper connection was made.

I recommend doing that before going too much further.

Viv
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Ok thanks I will check it again, worst case I will resolder  Atmega 328 from UNO :-)
Petr W

2016-11-25 5:41 GMT+01:00 viv.g [via BlueSaab Forum] <[hidden email]>:
Hey mate,

Encountered a few similar issues when going through the process.

In the end, it turned out it was a faulty solder connection somewhere. I went through and checked all connections and reheated them to ensure a proper connection was made.

I recommend doing that before going too much further.

Viv


If you reply to this email, your message will be added to the discussion below:
http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-v4-1-released-tp483p829.html
To unsubscribe from BlueSaab v4.1 released!, click here.
NAML

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

Re: BlueSaab v4.1 released!

Seth
Administrator
In reply to this post by PetrW
It looks like one of the pins on the crystal near the can chips is shorted to the case, which is ground. That shouldn't matter for the uploading but check that you don't have the same issue on the other crystal. No shorts, anywhere.

Also, make sure you're following the proper directions for burning a bootloader; you need to have ArduinoISP sketch uploaded to your Uno (you can't have anything connected to the uno while doing this), THEN you select the new programmer (Arduino as ISP), then connect to BlueSaab ISP header, then hit burn bootloader. You have to have the right 328 (if it's not a 328P, the chip signature won't match, but we're not there yet; it's a fixable problem).
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Ok thank you very much for help ! I ordereded parts from Mouser chip which came i Atmega 328 AU its correct ? Thanks Petr W

2016-11-25 14:19 GMT+01:00 Seth [via BlueSaab Forum] <[hidden email]>:
It looks like one of the pins on the crystal near the can chips are shorter to the case, which is ground. That shouldn't matter for the uploading but check that you don't have the same issue on the other crystal. No shorts, anywhere.

Also, make sure you're following the proper directions for burning a bootloader; you need to have ArduinoISP sketch uploaded to your Uno (you can't have anything connected to the uno while doing this), THEN you select the new programmer (Arduino as ISP), then connect to BlueSaab ISP header, then hit burn bootloader. You have to have the right 328 (if it's not a 328P, the chip signature won't match, but we're not there yet; it's a fixable problem).
2000 9-3 Viggen, AS3; iPhone 7+, iOS 10.1, BlueSaab v5.0, software v4.0b



If you reply to this email, your message will be added to the discussion below:
http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-v4-1-released-tp483p831.html
To unsubscribe from BlueSaab v4.1 released!, click here.
NAML

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

Re: BlueSaab v4.1 released!

Seth
Administrator
I think that’s the “wrong” chip, but it will still work, it will just take some more work to get it to work because when the software tries to upload, the chip signature won’t match (it looks for a 328P and a 328 won’t match). It’s just a matter of changing a small value to get it to upload, but it can be confusing. Don’t worry about that until it happens.

On Nov 25, 2016, at 08:27, PetrW [via BlueSaab Forum] <[hidden email]> wrote:

Ok thank you very much for help ! I ordereded parts from Mouser chip which came i Atmega 328 AU its correct ? Thanks Petr W

2016-11-25 14:19 GMT+01:00 Seth [via BlueSaab Forum] <<a href="x-msg://1/user/SendEmail.jtp?type=node&amp;node=832&amp;i=0" target="_top" rel="nofollow" link="external" class="">[hidden email]>:
It looks like one of the pins on the crystal near the can chips are shorter to the case, which is ground. That shouldn't matter for the uploading but check that you don't have the same issue on the other crystal. No shorts, anywhere.

Also, make sure you're following the proper directions for burning a bootloader; you need to have ArduinoISP sketch uploaded to your Uno (you can't have anything connected to the uno while doing this), THEN you select the new programmer (Arduino as ISP), then connect to BlueSaab ISP header, then hit burn bootloader. You have to have the right 328 (if it's not a 328P, the chip signature won't match, but we're not there yet; it's a fixable problem).
2000 9-3 Viggen, AS3; iPhone 7+, iOS 10.1, BlueSaab v5.0, software v4.0b



If you reply to this email, your message will be added to the discussion below:
http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-v4-1-released-tp483p831.html
To unsubscribe from BlueSaab v4.1 released!, click here.
NAML

SAAB 9-5 Aero 2002



If you reply to this email, your message will be added to the discussion below:
http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-v4-1-released-tp483p832.html
To start a new topic under Hardware, email [hidden email]
To unsubscribe from Hardware, click here.
NAML

NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
Hello all,
I tried change chip signature in avertude.conf but still I couldn´t burn bootloader. There can be possibility that I some how bricked chip with fuses and ext / int crystal settings.
SO finaly I used Atmega chip from my 3$ UNO clone and before unsoldering I also uppload CDC sketch to chip. I think this can be nice  source of prebooted chips for beginers which don´t have programing skills but must have soldering skill :-)

https://goo.gl/photos/wJMucr4FV8xd9XEU8


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

Re: BlueSaab v4.1 released!

Seth
Administrator
Are you using windows or mac? On windows, there are actually TWO locations for AVRDUDE.CONF and you have to modify the CORRECT one. And of course, the easy one to get to is the WRONG one. You have to navigate to a hidden folder in local_settings in your user folder, then navigate and find it there. If you modify that file, you should be able to adjust the signature to the chip that you have.

Of course, doing it your way works too :)
NC, USA
Reply | Threaded
Open this post in threaded view
|

Re: BlueSaab v4.1 released!

PetrW
thanks !  Yes I have widows and I changed wrong one :-)

2016-12-01 15:11 GMT+01:00 Seth [via BlueSaab Forum] <[hidden email]>:
Are you using windows or mac? On windows, there are actually TWO locations for AVRDUDE.CONF and you have to modify the CORRECT one. And of course, the easy one to get to is the WRONG one. You have to navigate to a hidden folder in local_settings in your user folder, then navigate and find it there. If you modify that file, you should be able to adjust the signature to the chip that you have.

Of course, doing it your way works too :)
2000 9-3 Viggen, AS3; iPhone 7+, iOS 10.1, BlueSaab v5.0, software v4.0b



If you reply to this email, your message will be added to the discussion below:
http://bluesaab-forum.2349123.n4.nabble.com/BlueSaab-v4-1-released-tp483p845.html
To unsubscribe from BlueSaab v4.1 released!, click here.
NAML

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

Re: BlueSaab v4.1 released!

homerisback
As I became, kind of, master in handling BlueSAAB v3.x (hardware and software) I decided to update my v4.2 with Karlis latest code.
I did it with the USB cable and selecting Arduino Uno as a board in Adruino IDE software... at that time I thought, "it won't work, I'll have to adjust settings, dig into parameters files, etc." BUT none of this was needed, I only had to select "download" and whoaaa O_O it did the job in seconds !

I knew that there was a big step in hardware between v3 and v4, and that's real !
We too often come on forums to say what's wrong but it's so pleasant to also mention when it's great !

Seth and Karlis, you are Gods !
Next step, burning bootloader to 328's on v5 I just finished to built :-D
Cheers
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!

Seth
Administrator
Glad it worked so easy! Thanks for the compliments; Karlis & I must be doing something right 😁

Let us know if you have any trouble burning the bootloader; it can be tricky.
NC, USA
12