2011-06-15, 20:12:00
Sorry, no joy.
If I reset my board and hit "Check for bl", it gives me the same error.
My board is intended for a use where the user will not have access to it to reset into the bootloader. I had to add some code to my application so that when it is desired to download new firmware, it enters a loop that will wait for the "hello" character and then, when it sees the "hello", it executes a software reset in order to run the bootloader. Then, when the GUI sends the "hello" again, the bootloader is running and communication is established. My code sees the "hello" and resets, but I still get the same error. If I use the RS-232 port, it works perfectly.
If the bootloader is not running, or the RS-422 is unplugged from the board, the "Check for bl" command retries until it times out and does not report a framing error.
If I look at the RS-422 signals with a scope, I see 0xc1 sent by the GUI. The bootloader responds with 0xc5, 0x02, 0x01, 0x4b. The GUI shows the framing error.
John
If I reset my board and hit "Check for bl", it gives me the same error.
My board is intended for a use where the user will not have access to it to reset into the bootloader. I had to add some code to my application so that when it is desired to download new firmware, it enters a loop that will wait for the "hello" character and then, when it sees the "hello", it executes a software reset in order to run the bootloader. Then, when the GUI sends the "hello" again, the bootloader is running and communication is established. My code sees the "hello" and resets, but I still get the same error. If I use the RS-232 port, it works perfectly.
If the bootloader is not running, or the RS-422 is unplugged from the board, the "Check for bl" command retries until it times out and does not report a framing error.
If I look at the RS-422 signals with a scope, I see 0xc1 sent by the GUI. The bootloader responds with 0xc5, 0x02, 0x01, 0x4b. The GUI shows the framing error.
John