Society of Robots - Robot Forum
Software => Software => Topic started by: rox2007 on January 17, 2010, 11:06:22 PM
-
So, i was tired last night and mistakenly plugged in 6v good juice into the 3.3v headers that are used for output on the AXON. Shortly after that the serial to usb chip burnt out.
I was left with using another UART the board for the BOOTLOADER but that did not work.
I changed the PIN config in FBOOT source and included the right header and it compiled but the FBOOT program never actually connects with the AXON when i try to load a program using the bootloader.
I would appreciate any help.
Thanks in advance
-
If the USB chip is burnt out, you need to use a hardware programmer to flash the Axon, there's no way around that.
Do you have a ISP programmer, or an Arduino board, as there USB to Serial chips can be used as an ISP programmer?
-
Sure, i did that. i modified the bootloader to use UART0 (at least i believe i did that) instead of UART1 which has the fried chip but the FBOOT pc program could not recognize the axon bootloader.
Note:
I tried uploading the bootloader to a spare atmega 168 i had lying around. That worked, but the PC program could not recognize the microcontroller.
-
I'm confused then. So you are able to flash the Axon using a ISP programmer with a new bootloader that uses Uart0?
-
Yes, but when i run the fboot.exe program to try and download code, the backslash just spins forever without connecting to the axon even after power cycling.
I double checked that UART0 was working fine.
I am using fast and tiny version 2.1.
-
What are you using to go from USB to TTL, or are you level shifting a COM port. What are you using to connect to Uart0 of your Axon?
-
i am using the FTDI breakout board from sparkfun.
which has a usb interface
-
Hmm, i have not edited the bootloader before, and it seems like that's the issue, so i can't help much beyond this.
If you have a ISP, why are you still using the bootloader anyway?
-
Sure you programmed the bootloader right?
Are you sure you uploaded the bootloader correctly? If you upload any other program, does it work fine? Tx/Rx not mixed up?
Since the USB chip fried, is anything still shorting? I recommend unsoldering the 3 pin diode next to it just in case. Its a tiny black chip with 3 pins sticking out, and relatively easy to unsolder. The USB chip is very difficult to unsolder, so removing the diode will cut power to it.
-
@Admin: I tested all the UART's by loading a program which sends a test string and they all work. I'm not too sure if i changed the right code in the bootloader.
Basically, i just switched the ports for the TX and RX pins in the bootloader to that of UART0 and recompiles it. Do you know of anything else i have to do?
@madsci1016: ISP programming is super slow compared to the bootloader and it's just more convenient using a bootloader.
-
@madsci1016: ISP programming is super slow compared to the bootloader and it's just more convenient using a bootloader.
Wow, i have experienced the exact opposite. Now that i use a ISP, i flash 2KB programs in 3 seconds by hitting the program button in Win AVR studio. It was taking me longer then that just to switch to the dos window. And i don't have to mess with switching the Axon On/Off to program.
-
IT seems a while back, Admin wrote a modified bootloader to use Uart 0 in this post ( near the bottom)
http://www.societyofrobots.com/robotforum/index.php?topic=5911.0 (http://www.societyofrobots.com/robotforum/index.php?topic=5911.0)
but the attainment link breaks.
Do you still have that admin?
-
@madsci1016: ISP programming is super slow compared to the bootloader and it's just more convenient using a bootloader.
Wow, i have experienced the exact opposite. Now that i use a ISP, i flash 2KB programs in 3 seconds by hitting the program button in Win AVR studio. It was taking me longer then that just to switch to the dos window. And i don't have to mess with switching the Axon On/Off to program.
It's weird, i'm not sure why it's slower but it is.
Also, it would be great to get Admin's modified bootloader to check what i did wrong.
-
Are we sure that the .exe supports the FTDI IC??? Just asking???
Or it's made only for the IC that AXON has by factory???
-
Are we use that the .exe supports the FTDI IC??? Just asking???
Or it's made only for the IC that AXON has by factory???
It does, i have used an FTDI with the bootloader before.
-
are you talking about the fboot.exe? I dont think its dependent on the IC.
by the way (to anyone that cares). Does the fact that i use windows7 have anything to do with my problem. Maybe i should recompile the exe
-
I have win 7 64 bit, and fboot.exe would not run at all, becasue it is a 16 bit program, and 64 bit windows 'anything' will not run 16 bit programs.
-
i have a 32 bit windows 7. I'll just go ahead and compile it on my platform
-
I think windows 7 cannot run 16 bit dos programs. So anyone who plans on using windows 7 with fboot should either try modifying the code (i'll try making a gui prog) or just run in windows xp sp2 compatibility mode.
I use windows xp at my lab and windows 7 at home, thats why i couldnt use it
damn! I tried using compatibility mode and it did not work.
-
@madsci1016: ISP programming is super slow compared to the bootloader and it's just more convenient using a bootloader.
I'm fairly sure its because you set it to be slow.
When you open up this window, set ISP frequency to 4MHz (click Settings at the bottom right):
(http://andersonmicro.com/wp-content/uploads/2009/04/avr_studio_7-300x186.jpg)