[NUC472/M453] Export IAR project and other bugfixes #3590

ccli8 · 2017-01-16T09:04:54Z

Description

This PR includes support for exporting IAR project and other bugfixes for NUMAKER_PFM_NUC472 and NUMAKER_PFM_M453 targets.

0xc0170

Code LGTM

bridadan · 2017-01-17T15:42:43Z

retest uvisor

/morph export-build

bridadan · 2017-01-17T15:43:28Z

/morph test

theotherjimmy

Tools changes look fine.

bridadan · 2017-01-17T16:30:39Z

/morph export-build

bridadan · 2017-01-17T17:02:45Z

/morph test

mbed-bot · 2017-01-17T17:24:30Z

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 85

Exporter Build failed!

mbed-bot · 2017-01-17T18:32:12Z

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1417

All builds and test passed!

bridadan · 2017-01-17T18:49:39Z

The IAR exporter failed for both the NUMAKER_PFM_M453 and the NUMAKER_PFM_NUC472. We use IAR version 7.8, what version are you using to test?

bridadan · 2017-01-17T23:20:20Z

This should fix #3417 if we can get IAR exporting working!

ccli8 · 2017-01-18T01:25:36Z

@bridadan I test with IAR 7.3. I'll try IAR 7.8.

ccli8 · 2017-01-18T03:12:17Z

@bridadan After upgrade to IAR EWARM 7.80, the export function is still OK for both NUMAKER_PFM_NUC472 and NUMAKER_PFM_M453 targets.

CCLi8@OANBE02023 MINGW32 /c/ccli8/iot/mbed/mbed-os/mbed-os-example-blinky (master)
$ mbed export -i iar -m NUMAKER_PFM_NUC472
c:\python27\lib\site-packages\fuzzywuzzy\fuzz.py:35: UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning
  warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')
Scan: .
Scan: FEATURE_BLE
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_LWIP
Scan: FEATURE_UVISOR
Scan: FEATURE_ETHERNET_HOST
Scan: FEATURE_LOWPAN_BORDER_ROUTER
Scan: FEATURE_LOWPAN_HOST
Scan: FEATURE_LOWPAN_ROUTER
Scan: FEATURE_NANOSTACK
Scan: FEATURE_NANOSTACK_FULL
Scan: FEATURE_THREAD_BORDER_ROUTER
Scan: FEATURE_THREAD_END_DEVICE
Scan: FEATURE_THREAD_ROUTER
Scan: FEATURE_STORAGE

But to develop/debug with the exported IAR project, post-export configuration e.g. debugger driver is needed.

It seems that the failure log has been deleted and I cannot see the details about the failure.

bridadan · 2017-01-18T15:34:51Z

@ccli8 The export function works just fine, it's when you try and build examples with IAR's build system (either via the command line or through the IDE) for that target where it fails.

For the NUMAKER_PFM_M453 we are just testing https://github.com/ARMmbed/mbed-os-example-blinky.

For the NUMAKER_PFM_NUC472, we are testing the following examples:

The way we test them is we import the example with mbed CLI, then we go to the mbed-os repo inside the project and pull in the fork that we're testing. You could do that for your fork to test your changes.

ccli8 · 2017-01-19T11:08:45Z

@bridadan The exported IAR project needs fix for debugging. Please follow the Debug with IAR EWARM guide.

Besides, could I build the exported IAR project by invocating scripts in mbed-os/tools? How to do that?

theotherjimmy · 2017-01-19T11:26:10Z

@ccli8 What fix do you need from the IAR exporter for debugging?

0xc0170 · 2017-01-19T14:41:33Z

@ccli8 What fix do you need from the IAR exporter for debugging?

I believe it is debugger driver. Is that correct @ccli8 ? When is this driver becoming part of IAR ?

theotherjimmy · 2017-01-19T14:59:13Z

Oh, you mean that you need a third party driver to be installed to debug with IAR. I had originally read something that implied "The IAR exporter has to change". Sorry about that.

bridadan

@ccli8 The export failure was caused by it failing to build because the field OGChipSelectEditMenu was incorrect. I've detailed the changes I had to make below.

Also @theotherjimmy do we have a place where we document custom setup instructions for debuggers?

bridadan · 2017-01-19T17:25:13Z

tools/export/iar/iar_definitions.json

@@ -157,5 +157,11 @@
    },
    "NCS36510":{
        "OGChipSelectEditMenu": "NCS36510\tONSemiconductor NCS36510"
+    },
+    "NUC472HI8AE": {
+        "OGChipSelectEditMenu": "NUC400AE series\tNuvoton NUC400AE series (NUC442AE,NUC472AE)"


Please change this line to:

"OGChipSelectEditMenu": "NUC472JI8AE\tNuvoton NUC472JI8AE"

@bridadan Please keep the OGChipSelectEditMenu setting. Install Nu-Link Driver (IAR) first before building the exported IAR project. The change wouldn't fix the error still per my test.

bridadan · 2017-01-19T17:27:09Z

tools/export/iar/iar_definitions.json

+        "OGChipSelectEditMenu": "NUC400AE series\tNuvoton NUC400AE series (NUC442AE,NUC472AE)"
+    },
+    "M453VG6AE": {
+        "OGChipSelectEditMenu": "M451AE series\tNuvoton M451AE series (M451AE,M452AE,M453AE,M451MAE)"


Please change this line to:

"OGChipSelectEditMenu": "M453VG6AE\tNuvoton M453VG6AE"

@bridadan same as above.

theotherjimmy · 2017-01-19T17:32:02Z

The platform page on the developer site and the export page in the handbook.

ccli8 · 2017-01-20T01:31:50Z

@bridadan I guess I know the failed point. Please install Nu-Link Driver (IAR) first to add these two targets' mcu information into your IAR's device database. It is necessary for both compiling and debugging.

ccli8 · 2017-01-20T01:42:42Z

@theotherjimmy @0xc0170

bridadan

@ccli8 I owe you an apology! I should have carried out all of your instructions before requesting changes. Installing the Nu-Link Driver (IAR) did indeed fix the issue.

However, is there anyway we can avoid the manual editing of the project file? We can't really add this to the CI if we have to manually edit it. Any thoughts @theotherjimmy?

theotherjimmy · 2017-01-20T16:38:47Z

However, is there anyway we can avoid the manual editing of the project file?

Do we need to do that? I was under the impression that we only needed to install a driver.

bridadan · 2017-01-20T16:42:25Z

According to the instructions here, the changes are necessary: https://github.com/OpenNuvoton/NuMaker-mbed-docs/blob/master/IAR/DEBUG_IAR.md#fix-debug-options-manually

Also, the next section "Check configurations in IAR EWARM IDE" has more changes that aren't being set by default with the mbed export command.

ccli8 · 2017-01-23T01:45:43Z

@bridadan @theotherjimmy Per my test on IAR EWARM 7.8, build is OK with just Nu-Link Driver (IAR) installed. Debugging support needs extra manual editing of the project file as above. Does your CI include debugging?

bridadan · 2017-01-23T08:11:20Z

@ccli8 I can confirm that it project builds ok without any manual modifications. Though there are a quite a few error messages that pop up when the project loaded. @ccli8 are they any plans to include the Nu-Link Driver in the upcoming releases of IAR?

ccli8 · 2017-01-23T09:39:07Z

@bridadan I can re-produce these errors. Currently, Nu-Link Driver is not scheduled to integrate into IAR and will still work as third-party plug-in.

bridadan · 2017-01-23T13:04:31Z

Thanks for the update @ccli8. I noticed that there is already a Nuvoton target that works in IAR without needing to install the Nu-Link driver. Is it still possible to debug with this target or are these changes necessary?

@sg- Do we have a policy on boards that require external dependencies to be installed for exporters to work besides the IDE themselves? In this case the build fails unless the Nu-Link Driver is installed. If this is fine then I can just install it on all the CI machines.

ccli8 · 2017-01-24T01:52:22Z

@bridadan where did you find such Nuvoton target? I find none of Nuvoton targets except I install Nu-Link Driver (IAR).

0xc0170 · 2017-01-27T11:25:57Z

@sg- Do we have a policy on boards that require external dependencies to be installed for exporters to work besides the IDE themselves? In this case the build fails unless the Nu-Link Driver is installed. If this is fine then I can just install it on all the CI machines.

@sg- @bridadan Any update? I would install the board requirements for CI, as it's not integrated within the tool.

bridadan · 2017-01-27T12:03:24Z

Sorry for my delayed response. The Nuvoton targets are definitely available in the IDE as of 7.8 (the version I'm using). I was able to find an old release note for version 7.6 and looks like the device is available there as well (NUC472JI8AE): http://supp.iar.com/FilesPublic/UPDINFO/011006/arm/doc/infocenter/device_support/Nuvoton.ENU.html#NUC400

I don't have a board with me now, but perhaps the debugging works without the need to install the Nu-Link driver in later versions?

0xc0170 · 2017-01-30T16:45:07Z

@ccli8 What od you think, can you update IAR specific device name as proposed by @bridadan above? Does debugging work?

bridadan · 2017-01-30T19:59:59Z

Hmm, so I've tried using the driver that is supplied by IAR and I've tried using the built-in target that's part of IAR 7.8. Both build ok, but I can't seem to get debugging working using the guide linked above. I keep getting this error:

Any ideas @ccli8? I can confirm the file that's in that error box exists.

ccli8 · 2017-02-02T02:51:49Z

Sorry for my late response @bridadan @0xc0170. Yes, Nuvoton device database is built into IAR 7.8 but Nu-Link debugger driver is not. The install/uninstall of Nu-Link Driver (IAR) will also overwrite/remove this built-in database, so I was confused and didn't find it at start. Anyway, debugging is not supported in clean IAR 7.8 without Nu-Link Driver (IAR) installed, and manual editing of the exported project file is necessary. Nuvoton's tool team is checking with IAR for integration of Nu-Link Driver (IAR) into IAR release. I will make necessary modification as soon as I have further information.

ccli8 · 2017-02-02T10:01:01Z

For IAR debugging error @bridadan, have you switched the board to Debug mode from Mass mode ? Without such switch, I can re-produce the same error as you.

ccli8 · 2017-02-06T01:25:12Z

@bridadan Do you get IAR debugging working now? Besides, IAR replied adding Nu-Link as built-in debugger is OK, but it requires upgrade from VS2008 to VS2015. Our tool team is estimating it and the work takes more than 2 months.

bridadan · 2017-02-06T16:52:32Z

Ah that was the missing part, thanks @ccli8. I can now debug once I do the manual modifications of the Project file.

@0xc0170 If we're ok with having the user do the IAR driver installation and editing the project file then I'll go ahead and add the driver to all the CI machines.

sg- · 2017-02-09T15:59:52Z

@0xc0170 If we're ok with having the user do the IAR driver installation and editing the project file then I'll go ahead and add the driver to all the CI machines.

@bridadan From what I've understood here that is what has to be done anyways to use Nuvoton boards / debuggers and IAR. Is this correct? If so, not ideal but CI updates and documentation on the exporter redirect page should be good enough.

bridadan · 2017-02-09T16:03:17Z

@sg- Sounds good, I'll get the CI machines equipped with the Nuvoton IAR Driver.

bridadan · 2017-02-09T16:31:51Z

/morph export-build

bridadan

Test results look good!

Ports for Upcoming Targets Fixes and Changes 3590: [NUC472/M453] Export IAR project and other bugfixes ARMmbed/mbed-os#3590 3740: STM32L4 HAL update for RTC Wake Up Timer ARMmbed/mbed-os#3740 3739: STM32F7 : remove multiple HSE_VALUE define value ARMmbed/mbed-os#3739 3759: STM32: spi_frequency table index fix ARMmbed/mbed-os#3759 3779: NCS36510: Fix the sporadic semaphore timing issue ARMmbed/mbed-os#3779 3806: NXP KL43Z/KL27Z: fix spi format bits check ARMmbed/mbed-os#3806 3814: NCS36510: I2C idle delay of 1us ARMmbed/mbed-os#3814 3803: Bug fix of initial value of interrupt edge in "gpio_irq_init" again ARMmbed/mbed-os#3803

ccli8 added 3 commits January 16, 2017 09:48

[NUC472/M453] Remove power-down support from us_ticker

453f60e

[NUC472/M453] Change sbrk() allocation to be 32-byte aligned

0a0b326

[NUC472/M453] Support exporting IAR project

867decb

0xc0170 approved these changes Jan 16, 2017

View reviewed changes

0xc0170 added the needs: CI label Jan 16, 2017

theotherjimmy approved these changes Jan 17, 2017

View reviewed changes

bridadan suggested changes Jan 19, 2017

View reviewed changes

bridadan added the needs: work label Jan 19, 2017

bridadan reviewed Jan 20, 2017

View reviewed changes

bridadan mentioned this pull request Jan 25, 2017

[Exporter] [TLS-Client] : Platform not supported by IAR. #3633

Closed

bridadan approved these changes Feb 9, 2017

View reviewed changes

bridadan added ready for merge and removed needs: CI needs: work labels Feb 9, 2017

sg- added release-version: 5.3.6 and removed ready for merge labels Feb 13, 2017

sg- merged commit d8151d7 into ARMmbed:master Feb 13, 2017

[NUC472/M453] Export IAR project and other bugfixes #3590

[NUC472/M453] Export IAR project and other bugfixes #3590

Conversation

ccli8 commented Jan 16, 2017

Description

0xc0170 left a comment

Choose a reason for hiding this comment

bridadan commented Jan 17, 2017

bridadan commented Jan 17, 2017

theotherjimmy left a comment

Choose a reason for hiding this comment

bridadan commented Jan 17, 2017

bridadan commented Jan 17, 2017

mbed-bot commented Jan 17, 2017

Result: FAILURE

Output

mbed-bot commented Jan 17, 2017

Result: SUCCESS

Output

bridadan commented Jan 17, 2017 • edited Loading

bridadan commented Jan 17, 2017

ccli8 commented Jan 18, 2017

ccli8 commented Jan 18, 2017

bridadan commented Jan 18, 2017

ccli8 commented Jan 19, 2017

theotherjimmy commented Jan 19, 2017

0xc0170 commented Jan 19, 2017 • edited Loading

theotherjimmy commented Jan 19, 2017

bridadan left a comment

Choose a reason for hiding this comment

bridadan Jan 19, 2017

Choose a reason for hiding this comment

ccli8 Jan 20, 2017

Choose a reason for hiding this comment

bridadan Jan 19, 2017

Choose a reason for hiding this comment

ccli8 Jan 20, 2017

Choose a reason for hiding this comment

theotherjimmy commented Jan 19, 2017

ccli8 commented Jan 20, 2017

ccli8 commented Jan 20, 2017

bridadan left a comment

Choose a reason for hiding this comment

theotherjimmy commented Jan 20, 2017

bridadan commented Jan 20, 2017

ccli8 commented Jan 23, 2017

bridadan commented Jan 23, 2017

ccli8 commented Jan 23, 2017

bridadan commented Jan 23, 2017

ccli8 commented Jan 24, 2017

0xc0170 commented Jan 27, 2017

bridadan commented Jan 27, 2017

0xc0170 commented Jan 30, 2017 • edited Loading

bridadan commented Jan 30, 2017

ccli8 commented Feb 2, 2017

ccli8 commented Feb 2, 2017

ccli8 commented Feb 6, 2017

bridadan commented Feb 6, 2017

sg- commented Feb 9, 2017

bridadan commented Feb 9, 2017

bridadan commented Feb 9, 2017

bridadan left a comment

Choose a reason for hiding this comment

bridadan commented Jan 17, 2017 •

edited

Loading

0xc0170 commented Jan 19, 2017 •

edited

Loading

0xc0170 commented Jan 30, 2017 •

edited

Loading