mbed export -i IAR -m NCS36510 not working with mbed-os-5.2.2(a1c0840)

[radhika-raghavendran]

Description

• Type: Bug
• Related issue:
• Priority: Major

---

Bug

Target
NCS36510

Toolchain:
IAR

Toolchain version: 7.80.2

mbed-cli version:
0.8.9

Steps to reproduce

git checkout a1c0840
mbed export -i IAR -m NCS36510

[bridadan]

Hi @radhika-raghavendran, sorry for the inconvenience and thanks for raising this issue. I just took a look at this and it looks the root cause of this was a check that was added to the IAR exporters to require CMSIS pack support: https://github.com/ARMmbed/mbed-os/blob/master/tools/export/iar/__init__.py#L33.

The CMSIS pack is being used during the export process to automatically set the debugger for the project: https://github.com/ARMmbed/mbed-os/blob/master/tools/export/iar/__init__.py#L116

This has the added benefit of making debugging targets far easier out-of-the-box, but it does now require that targets must have a CMSIS pack.

[maclobdell]

@radhika-raghavendran, Our plan going forward is to leverage cmsis packs for exporter information instead of maintaining separate data sets. It seems that we made this change abruptly in 5.2, thus requiring cmsis packs. We will investigate if we can implement a work around, but the best case would be if you had a preliminary cmsis pack available to test.

[maclobdell]

oops, accidentally closed the issue inadvertently. Just reopened.

[radhika-raghavendran]

@bridadan @maclobdell
I thought CMSIS pack was exclusively meant for Kiel MDK IDE. Is there a dependency of IAR on CMSIS pack? Also, is there any information or documentation available on CMSIS pack generation for new devices, which can be used for Kiel MDK, IAR and Eclipse IDEs? There is a link describing CMSIS pack but it addresses only Kiel MDK, http://www.keil.com/pack/doc/CMSIS/Pack/html/createPack_DFP.html

[maclobdell]

@radhika-raghavendran I discussed this with @sarahmarshy who is working on the exporters. cmsis pack isn't really needed for IAR IDE itself, but the exporter scripts are referencing cmsis packs to set default settings in the generated project (like default debug interface). This can potentially be done in another way, or maybe if pack is not present, it can just not set a default debugger interface. We will investigate this and hopefully have a workaround soon.

[maclobdell]

Sarah just pushed a branch with a patch that could be a workaround to this issue. It has not been tested yet. sarahmarshy@bbb9744
If everything works, we can make a pull request to get this on the master branch.

[radhika-raghavendran]

@maclobdell @sarahmarshy
After bringing in the changes in your fork into the mbed-os 5.2.2 release code base, exporting to IAR for NCS36510 is now working. Can you bring this into the main mbed-os repo, so that I can use the main mbed-os branch for development?

[radhika-raghavendran]

Is the proposed fix merged into the main mbed-os repository? Is there a particular version of mbed-os which I can check?

[danclement]

@radhika-raghavendran I just imported the mbed blinky example, made sure all my pip tools were updated, and this issue still persists. This is with the current mbed OS master.

I replaced the file that is in the branch Mac mentioned above and it did seem to export correctly but IAR could not open the project file created.

@maclobdell can you give us some guidance on @radhika-raghavendran 's question about versioning?

[theotherjimmy]

@radhika-raghavendran @danclement I have not seen any PRs yet, and the file that the above patch modifies remains unmodified in master. I don't think it has been merged yet.

@sarahmarshy The diff looks good to me Could you create a PR for it? (I'll approve the changes)

[radhika-raghavendran]

@danclement
The pull request will need to be made on project generator side and only after the merge to main branch will the issue be resolved.
As mentioned in a previous comment of mine, project generation is working with the changes suggested by @sarahmarshy
In case you would like to test before the merge to main branch happens, please use the modifications mentioned by @maclobdell and @sarahmarshy

[sarahmarshy]

Project generator is deprecated. This logic lives in mbed-os tools now. Please see the link to the PR above.

[radhika-raghavendran]

@sarahmarshy Can I uninstall project generator and project generator definitions now?
Also, your suggested changes are working and I am able to export the project to IAR. Thank you.

[sarahmarshy]

Yes, you can!

[danclement]

Radhika, I have already gone back to 5.2.2 with the patch from Sarah and I can confirm that I can export an IAR project, open it and compile, and download and debug the NCS36510. Thank you all for the help. Best Regards, Dan Clement From: radhika-raghavendran [mailto:[email protected]] Sent: Thursday, December 01, 2016 9:04 PM To: ARMmbed/mbed-os <[email protected]> Cc: Dan Clement <[email protected]>; Mention <[email protected]> Subject: Re: [ARMmbed/mbed-os] mbed export -i IAR -m NCS36510 not working with mbed-os-5.2.2(a1c0840) (#3286) @danclement<https://github.com/danclement> The pull request will need to be made on project generator side and only after the merge to main branch will the issue be resolved. As mentioned in a previous comment of mine, project generation is working with the changes suggested by @sarahmarshy<https://github.com/sarahmarshy> In case you would like to test before the merge to main branch happens, please use the modifications mentioned by @maclobdell<https://github.com/maclobdell> and @sarahmarshy<https://github.com/sarahmarshy> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#3286 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANogy7G7DMfEd7-gu-c5sQIvcle1KD7Qks5rD5jAgaJpZM4K2Jqy>.

[0xc0170]

I believe this issue can be closed.