- #Gertduino avrdude programming install
- #Gertduino avrdude programming code
- #Gertduino avrdude programming Pc
#Gertduino avrdude programming code
I didn't check out the code for the Atmel boot program. As I understand it, the baud rate is fixed (at least for the optiboot bootloader), so I don't understand how other posters have managed to get it working with two different baud rates. Just one thing about bootloader before I leave it, though. A missing bootloader would only be possible if you'd installed completely over ICSP, so I'll take your word for it that the sketch was uploaded via USB and that a missing bootloader isn't to blame.
#Gertduino avrdude programming install
I've been reading everything I can find about how the bootloader and ICSP works over the last few days and as I understand it, if you hadn't burned the bootloader first, you wouldn't have been able to install the v1.5 show_main software over USB at all afterwards. So the possibility of missing bootloader is quite low.īased on that info, it seems that the problem can't be that the bootloader is missing after all. In our production line, we are flashing the boot loader via ICP connector first.Īnd program the display application via USB. The programmer seems to think that the device ID of the SHOW2 is blank when I try programming it like this.Īnyway, it's too complex to try to explain tonight, so I'll report on my new findings tomorrow. I'll follow up tomorrow because I tried fixing that with an ICSP connection via my older SHOW but I ran into other problems. I'm pretty sure that the problem is a lack of (compatible) boot loader on the ATMega328 itself. I appreciate the suggestions, but I think that my original post already ruled out cable (since I used the supplied one, which worked) or port problems. I'm sad to say that this wouldn't be the first time I've had problems with "official" bootloader code (ie, hidden/secure partition on Linux emmc wouldn't work) so I don't rule it out.
#Gertduino avrdude programming Pc
Maybe it should have been written to the device in the factory, but either there was a problem writing to the flash (ie, no bootloader) or the version of the bootloader that was installed is incompatible with my Arduino IDE (tried versions 1.0.1 on my PC and 1.0.5 as installed on the emmc when I got the XU3 Lite machine yesterday the version of avrdude is also listed in my first post). The remaining thing you say is to do with bootloader for the ATMega328p (not cp2104). If the connection works and the USB tty device is created, then I can rule out either USB port or cable as the cause of the problem. The udev process creates the appropriate /dev/ttyUSB device. Recognising the USBUART device (cp2104) isn't the problem. So I guess that USB cable or MicroUSB port is don't work. If you connect your odroid-show2 to host, you should be able to find /dev/ttyUSB*.Īlso, cp2104 bootloader is writed to factory. If my guess is right, and there's no bootloader code on the boards, what can I do? I'm guessing that this isn't what should happen. When I send the avrdude command the SHOW 2 reboots, but it goes straight into the "Hello ODROID-SHOW! (v1.5)" screen. I suspect that the problem might actually be missing bootloader code on my new boards. I tried a shorter USB cable than the one supplied, but then the cp2104 doesn't even get detected. I get the same result whether connecting from XU or my desktop PC. The jumper between the USB and screen is in place when I do this. I have an older revision of the SHOW and it has no problem. User configuration file does not exist or is not a regular file, skippingĪvrdude: stk500_recv(): programmer is not respondingĪvrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00 User configuration file is "/home/odroid/.avrduderc" System wide configuration file is "/etc/nf" Code: Select all $ avrdude -c arduino -p m328p -P /dev/ttyUSB* -b 9600 -vĪvrdude: Version 6.0.1, compiled on at 14:25:10
0 kommentar(er)
