Mbed Studio 1.4.2 linter bugs

Hello,

That does not surprise me in the slightest. Two years on, some things still are not fixed. See this post here for instance: https://forums.mbed.com/t/target-restrict-size-doesnt-pad-out-the-bin-file/14553/3. Simply ridiculous.

The fact that I am still getting notifications from this forum two years after last working with this despicable piece of software, says a lot to me.

If you are thinking of using the bootloader feature of Mbed OS, do not bother, that’s all.

Kind regards,

Tijn Losekoot



|
Target.restrict_size doesn’t pad out the .bin file
I use target.restrict_size like so in the mbed_app.json file. { “target_overrides”: { “MAX32630FTHR”: { “target.device_name”: “MAX32630”, “target.bootloader_supported”: true, “target.pad_to_restrict_size”: true, “target.restrict_size”: “0x16000” } } } I even added the extra parameter “pad_to_restrict_size” after coming across this old Github post: Add padding up to restrict_size by statropy · Pull Request #11043 · ARMmbed/…
forums.mbed.com
|

  • | - |

======================================================================================================================================== E-maildisclaimer: Aan dit bericht, waaronder ook de eventuele bijlagen worden bedoeld, kunnen geen rechten worden ontleend. Dit bericht is uitsluitend bestemd voor de geadresseerde en bevat persoonlijke en vertrouwelijke informatie. Het bekend maken, kopieren en verspreiden van een bericht dat niet voor u bestemd is, is niet toegestaan. Als u dit bericht per ongeluk heeft ontvangen, verzoeken wij u vriendelijk het direct te vernietigen en de afzender te informeren. Twijfelt u over de juistheid of volledigheid van dit bericht? Neem dan contact op met de afzender. ======================================================================================================================================== This message and any associated attachments cannot be deemed as legally binding under any circumstances. This message is intended for the exclusive use of the person(s) mentioned as recipient(s) and contains personal and confidential information. Directly or indirectly copying, disclosing, distributing, printing, publicising and/or in any way using this message or any part thereof by any means is strictly prohibited if you are not the intended recipient(s). If you have received this message in error, please notify the sender and delete this message from your system immediately. If you are in doubt regarding the correctness and/or completeness of this message, please contact the sender.