Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootloader on MX working with latest LibopenCM3 #8

Open
OpenUAS opened this issue Jul 29, 2015 · 3 comments
Open

Bootloader on MX working with latest LibopenCM3 #8

OpenUAS opened this issue Jul 29, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@OpenUAS
Copy link
Contributor

OpenUAS commented Jul 29, 2015

AS a user I want a simple way to upload my AP software to the AP board. the newer Lisa v2 MX has an F4. THe working of flasing by USB are not tested and know to be problematic. Will dig up a board and start testing.

There already exists a bootloader for Lisa MX https://github.com/podhrmic/aggieair-bootloader but it still has to be merged to the main repo, since it is using older version of libopencm3 and needs to be updated.

@podhrmic
Copy link
Member

podhrmic commented Aug 4, 2015

Looks like the main difference is not in the version of the libopencm3, but rather in the makefile process. Using latest libopencm3 (the same as paparazzi master), I can compile luftboot for Lisa MX, and upload code (yes it says *upload successfully completed), but then the code never starts. When I bypass the bootloader by providing 5V on input (and not using USB cable), the program doesn't start.

At the same time, the bootloader from https://github.com/podhrmic/aggieair-bootloader works perfectly. I ll make a pull request with the code changes.

@flixr
Copy link
Member

flixr commented Aug 5, 2015

Of course the flags you have to set in the makefile are different for F1 and F4...

@OpenUAS
Copy link
Contributor Author

OpenUAS commented Aug 25, 2015

If you wanted to experiment with the experimental Lisa MX bootloader some notice sometimes uploading the bootloader will lock the flash...
and you won't be able to override the bootloader via SWD.

In that case this sequence of commands seems to work:
-in gdb-

target extended-remote /dev/ttyACM0
mon swdp_scan
attach 1
mon option erase
mon erase_mass
disconnect

@OpenUAS OpenUAS added this to the v1.2 milestone Nov 1, 2015
@OpenUAS OpenUAS self-assigned this Nov 29, 2017
@OpenUAS OpenUAS added the Major label Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants