Get the SoR Robotics Android App on Android Market for FREE. See this forum post for details.
0 Members and 1 Guest are viewing this topic.
rprintfInit(uart0SendByte);//change UART to bluetooth rprintf("Y=%d U=%d V=%d\r\n\r\n",Y_mean, U_mean, V_mean);
this bootloader can only connect with com ports 1 to 4. The developer of the bootloader for some odd reason thought there isn't anything wrong with this decision . . . If you need a different port, go to the com port settings and change the port you are using.
Oh, reminds me . . .You already own a MK II programmer, so you don't need to use the bootloader if you don't want. Just plug into the ISP header and program the Axon directly.The bootloader is just there to save people the $36 of buying a programmer.Using the programmer will overwrite the bootloader, but you can always put it back on in the future if you wanted.btw - I test *every* Axon individually, every signal pin, the USB, the bootloader, everything. It worked when it was shipped
It seems like it uploaded the hex file after I changed it fromo com1 to com3
I don't want to use a programmer with my Axon.
QuoteIt seems like it uploaded the hex file after I changed it fromo com1 to com3Your Axon was connected to com3 In the future, just use step 3 here to determine your com port:http://www.societyofrobots.com/axon/axon_getting_started_hardware.shtml
QuoteI don't want to use a programmer with my Axon.Just curious why . . . I personally prefer to use a programmer with the Axon. The bootloader is a few seconds slower, and requires me to type in a command prompt (I'm lazy ). Also, since I also use the USB for debugging, its annoying to turn hyperterminal on/off when I want to reprogram with the same comport.