Export: uvision5 + STM32 does not flash

[rspelta]

Description

• Type: Bug
• Targets "tested": NUCLEO_L476ZI, SILICA_SENSOR_NODE
• IDE used: uVision 5.24
• Project: mbed-os-example-blinky (lastest version)

Marcelo has asked to me to open this issue.
cc: @MarceloSalazar

Issue:
When I export the project (mbed-os-example-blinky) for uVision5 and I try to debug it, I get this error:

it’s something to do with the flash algorithm not being set correctly. It seems that the project is exported wrongly.

My temporary solution:
I find out a workaround setting manually the project. Here my steps:

1. mbed import https://github.com/ARMmbed/mbed-os-example-blinky
2. mbed export -i uvision5 -m SILICA_SENSOR_NODE
3. open the project and if needed download the libreries required
4. Even if you have this error, ignore it
   
5. go to "Project -> Options for the target 'mbed-os-example-blinky'"
6. Click on "Debug" tab
   
7. Click on "Settings" button, it is near "Use: ST-Link Debugger"
8. Select "Connect: with pre-reset" (at the bottom of the form, in "Connect & Reset Options")
   
9. Click on "Flash download" tab
10. Click on "add" button
    
11. Select "STML4xx 1MB Flash", it is the algorithm. Now it is setted correctly!
    

Side note: When I open the project in uvision, it complains about a missing device pack for STM32L4 even though it HAS been installed. Even if you try and re-install the pack completely, it still complains every time you open the project. About this issue seems you already know this problem and it will be fixed in the next release.

[theotherjimmy]

Thanks for the detailed description of the workaround! I'll take a look at this in the coming days. I may not have time this week, but you should certainly hear from me sometime next week.
[Mirrored to Jira]

[theotherjimmy]

@rspelta @MarceloSalazar I was able to track down part of this issue. Could you take a look at #5489 for me?
[Mirrored to Jira]

[cmonr]

@MarceloSalazar Fyi, we removed the IOTMORF-2318 comment to make sure the issue script doesn't do weird things.
[Mirrored to Jira]

[adbridge]

Internal Jira reference: https://jira.arm.com/browse/IOTCORE-244