The `mtb4c` project of the application does not work properly

robotology / icub-firmware

iCub Firmware

Other

11 stars 29 forks source link

The `mtb4c` project of the application does not work properly #507

Closed marcoaccame closed 1 week ago

marcoaccame commented 2 weeks ago

During the activity of #494 we noticed that the mtb4c project of the application does not allow to download code to the target. Further tests have shown that the produced binary when directly programmed w/ STlink onto the board prevents the mtb4c to execute. And the FirmwareUpdater does not program the binary.

It may be that the application project has some settings that produce the binary out of the allowed range of FLASH.

It is to be investigated further.

cc @simeonedussoni

simeonedussoni commented 2 weeks ago

To be more precise:

the application can be flashed only on flash erased status
- some times a failed to erase memory error is triggered
the bootloader is to be flashed after the application is flashed
after this sequence seems that the MTB4C works fine both with CANREAL and with the EMS under robotolgy environment

marcoaccame commented 1 week ago

On Tuesday Sept, 3 @simeonedussoni, @SanLordKevin and I thoroughly tested the mtb4c and concluded that it is all right:

[x] compiled bootloader and application,
[x] programmed FLASH w/ ulink pro and w/ stlink,
[x] updated application w/ FirmwareUpdater using devel's binary and the freshly compiled one, both normal and w/ macro for 5th finger enabled.

So, everything is all right.