3 replies to this topic

[Corvus Corax]

I am trying to flash the "next" firmware on my beta openpilot and ahrs boards.

With the OpenPilot board both bootloader-updater and firmware update seem to work right.

With the AHRS however this happens. The board gets detected, the uploader erases the flash rom, thenattempts uploading:

Quote

[16:08:13.644] [DEBUG] "DFUidle"                        qdebug
[16:08:13.650] [DEBUG] Starting Firmware Uploading...                        qdebug
[16:08:13.650] [DEBUG] Bytes Loaded= 10224                        qdebug
[16:08:13.664] [DEBUG] NEW FIRMWARE CRC= 891687276                        qdebug
[16:08:13.664] [DEBUG] Number of packets: 183  Size of last packet: 8                        qdebug
[16:08:14.661] [DEBUG] 64  bytes sent                        qdebug
[16:08:14.661] [DEBUG] Erasing memory                        qdebug
[16:08:14.674] [DEBUG] StatusRequest:  64  bytes sent                        qdebug
[16:08:17.700] [DEBUG] StatusRequest:  64  bytes received                        qdebug
[16:08:17.704] [DEBUG] StatusRequest:  64  bytes sent                        qdebug
UPLOADING[>                                                 ]   0%     [16:08:17.708] [DEBUG] StatusRequest:  64  bytes received                        qdebug
[16:08:17.708] [DEBUG] Erase returned:  ""                        qdebug
[16:08:17.708] [DEBUG] Start Uploading: 183 4Bytes                        qdebug
UPLOADING[==>                                               ]   4%     [16:08:27.739] [DEBUG] StatusRequest:  -110  bytes sent                        qdebug
[16:08:37.740] [DEBUG] StatusRequest:  0  bytes received                        qdebug
[16:08:37.741] [DEBUG] Upload failed (upload data)                        qdebug
[16:08:37.741] [DEBUG] UploadData returned: "abort"                        qdebug

and then gets this "abort" error.


Manually flashing the bootloader with make bl_ahrs_program works and the board gets detected again:

OpenPilot INS
Device ID: 201
HW Revision: 1
FGlash Access: RW
BL version: 0
Max code size: 122780

when I try to flash trhe firmware, again I get:

Quote

[16:17:06.090] [DEBUG] EnterDFU:  64  bytes sent                        qdebug
[16:17:06.094] [DEBUG] StatusRequest:  64  bytes sent                        qdebug
[16:17:07.138] [DEBUG] StatusRequest:  64  bytes received                        qdebug
[16:17:07.138] [DEBUG] "DFUidle"                        qdebug
[16:17:07.144] [DEBUG] Starting Firmware Uploading...                        qdebug
[16:17:07.144] [DEBUG] Bytes Loaded= 82000                        qdebug
[16:17:07.158] [DEBUG] NEW FIRMWARE CRC= 1669951510                        qdebug
[16:17:07.158] [DEBUG] Number of packets: 1465  Size of last packet: 4                        qdebug
[16:17:08.154] [DEBUG] 64  bytes sent                        qdebug
[16:17:08.155] [DEBUG] Erasing memory                        qdebug
[16:17:08.166] [DEBUG] StatusRequest:  64  bytes sent                        qdebug
[16:17:11.193] [DEBUG] StatusRequest:  64  bytes received                        qdebug
[16:17:11.197] [DEBUG] StatusRequest:  64  bytes sent                        qdebug
UPLOADING[>                                                 ]   0%     [16:17:11.202] [DEBUG] StatusRequest:  64  bytes received                        qdebug
[16:17:11.202] [DEBUG] Erase returned:  ""                        qdebug
[16:17:11.202] [DEBUG] Start Uploading: 1465 4Bytes                        qdebug
[16:17:21.231] [DEBUG] StatusRequest:  -110  bytes sent                        qdebug
[16:17:31.233] [DEBUG] StatusRequest:  0  bytes received                        qdebug
[16:17:31.233] [DEBUG] Upload failed (upload data)                        qdebug
[16:17:31.233] [DEBUG] UploadData returned: "abort"                        qdebug

It must be a bootloader issue. When I use bootloaders from the "master" trunk, there are no errors when uploading the AHRS firmware.


Edit: I suspect it to be a bl_openpilot issue. Switching the AHRS bootloader is not enough, I need to downgrade bl_openpilot to "master" in order to update the AHRS firmware.

[Corvus Corax]

I think Stac is working on this, should be resolved soon

[LemaLife]

has this issue been solved. I'm getting the same thing trying to update my board with the VCP firmware.

[PT_Dreamer]

LemaLife, on 13 November 2011 - 03:27 PM, said:

has this issue been solved. I'm getting the same thing trying to update my board with the VCP firmware.

That can't be the same issue, this was about the AHRS, and it can't use the VCP firmware...mainly because it doesn't have a USB plug.