Sysprogs forums › Forums › VisualGDB › nxp lpc55s69 import error
- This topic has 9 replies, 2 voices, and was last updated 4 years, 7 months ago by makurasian.
-
AuthorPosts
-
April 29, 2020 at 12:32 #27991makurasianSpectator
Hi,
I am trying to import a nxp board lpc55s69 toolchain to visualgdb. It seems to me that the actual SDK Version 2.7.1. 2020-02-24 from the sdk builder is not supported because after import some headers are not found and compile errors appears.
Which version of the SDK should be used with the actual VisualGDB?
Thanks
April 29, 2020 at 17:00 #27992supportKeymasterHi,
As every device-specific SDK generated by SDK builder is different from others, indeed some SDK versions or some devices may not be imported properly. As long as this is an MCUXPresso SDK, it is fully covered by our support. Please attach (or send to our support) the SDK archive and let us know the device name and the sample you pick from the wizard, and we will update our importer plugin to handle it correctly.
April 29, 2020 at 17:27 #27993makurasianSpectatorTake the latest SDK e.g. “SDK_2.7.1_LPCXpresso55S69” and select USB. If you have done this every USB example doesn’t work e.g. “lpcxpresso55s69_host_suspend_resume_hid_mouse_freertos”.
I tried it also with SDK “SDK_2.6.3_LPCXpresso55S69” with similar results.
I always get the following erros:
Error: selected processor does not support requested special purpose register — `mrs r3,primask’
Error: selected processor does not support `cpsid i’ in ARM mode
April 29, 2020 at 17:29 #27994supportKeymasterNo problem. Once you send us the SDK archive, we will investigate this.
April 29, 2020 at 17:51 #27996makurasianSpectatorThe file size is over 20MB and is to large to sent. Build it be yourself or give me an other way to upload.
April 29, 2020 at 18:20 #27997April 30, 2020 at 04:16 #28000supportKeymasterThanks, we have reproduced the problem. Indeed, the new SDK uses a slightly different format in order to accommodate multi-core devices, and our SDK importing logic is not handling it correctly.
Due to the considerable changes to the SDK structure, it will take us about a week to fully update our SDK importer and test it. We will publish an update here once it is ready.
April 30, 2020 at 04:50 #28001makurasianSpectatorThank you for the information and the great support!
Yes, I also thought on this multicore problem and how to make a project with VisualGDB. Spontaneously I would make two project in one solution. One for core0 and one for core1. It would be great if you make a short description how this can be done with VisualGDB, if you have corrected the importer.
Thanks again
Manfred
May 3, 2020 at 02:01 #28023supportKeymasterOK, we have updated VisualGDB to work with the latest MCUXpresso SDK: VisualGDB-5.5.5.3597.msi
For multi-core devices, it will create a separate device entry for each core (e.g. LPC55S69_CM33_CORE0), so you can choose a specific core when creating a project.
Please note that the example you mentioned (lpcxpresso55s69_host_suspend_resume_hid_mouse_freertos) does not build under the MCUXpresso IDE due to an error in the SDK definition. It will also not build with VisualGDB unless you manually resolve the build errors (same way as with the MCUXpresso IDE). Examples that build with MCUXpresso IDE will also build with VisualGDB.
Please refer to the regular Visual Studio documentation for steps on creating multiple projects in the same solution, they will work with VisualGDB as well.
May 4, 2020 at 09:39 #28044makurasianSpectatorIt didn’t work. Try it with a segger probe and you will see what’s going wrong.
Target device: LPC55S69JBD100_CM33_C0
The device is unknown.
And also it comes an error Toolchain test failed. Failed to link a test program: c:\SysGCC\arm-eabi\….
VisualgGDB version: 5.5.5.3597
- This reply was modified 4 years, 7 months ago by makurasian.
-
AuthorPosts
- You must be logged in to reply to this topic.