July 8, 2019 at 13:03 #25305
there are very useful tool – “Embedded Memory Explorer”, but it can show only two types of memory – “FLASH”, and “RAM”
Some MCU (like NXP i.MX RT1050) has three or more non-contiguous RAM regions.
We are trying to add these regions (ITC, DTC, OC SRAM) as “Additional Memories” in VisualGDB Project Properties, but got error (see attachements).
Now we found workaround to see all memory regions – modifiy RAMBase and RAMSize values in nxp_rt1050.xml
But this method is very inconvenient. Do you know another way to see all RAM regions in the Embedded Memory Explorer?July 9, 2019 at 00:31 #25316
The Additional Memories page should normally work, so most likely you are using some combination of settings that triggers a bug on our side. If you could reproduce this on a “LEDBlink” project created from scratch and send us the related files (ensure you clean the project before packing it), we should be able to release a hotfix for this promptly.July 9, 2019 at 11:19 #25324
No problem, I can show video (see attachments). Also you can download this video here: https://yadi.sk/i/NNkNbYOWUSVFLg
I created new project LEDBlink for one of supported MCU.
Used latest VisualGDB 5.4R10 (build 3225), and VisualGDB package manager has no updates.
I can provide any additional information, if needed. Thanks!
July 9, 2019 at 21:11 #25330
- This reply was modified 1 week, 5 days ago by Yuriy.
Thanks for the detailed description. We have pinpointed the problem and fixed it in this build: VisualGDB-220.127.116.1128.msiJuly 10, 2019 at 13:46 #25338
Thanks, now “Additional memories” works better. In the example project “LEDBlink” now it’s possible to add new RAM.
In our project it still not work, but error more clear now:
VisualGDB version: 18.104.22.16828
------------------ System.ArgumentException ------------------
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.GetFullPathInternal(String path)
at u72.x1(g8 b, EmbeddedProfile c, IProjectEditContext a)
at u72.f_4(de b, Object a)
at d7.q(zp b, IProjectEditContext c, kv1 a)
at d7.j(zp b, kv1 a)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.i(Boolean c, y3 d, String a, Action b)
at VisualGDB.Common_GUI.WPF.ProjectPropertiesWindow3.Apply_Click(Object sender, RoutedEventArgs e)
This error appears for exactly the same memory parameters, as in example project.
Anyway, our issue was solved – now we can use “Embedded Memory explorer” for all RAM regions by modifying nxp_rt105.xml file
After modifying nxp_rt105.xml I can see additional memory in “Additional memories” dialog, but I can’t add new items and can’t modify existing memories (added manually to nxp_rt105.xml):C++12345678910111213141516171819202122<ExtraMemories><ExtraMemoryDefinition><Name>RAM_ITC</Name><Address>0</Address><Size>131072</Size><Type>RAM</Type><ContainsText>true</ContainsText><ContainsData>true</ContainsData><ContainsBSS>true</ContainsBSS><PreserveUnusedSymbols>false</PreserveUnusedSymbols></ExtraMemoryDefinition><ExtraMemoryDefinition><Name>RAM_DTC</Name><Address>536870912</Address><Size>131072</Size><Type>RAM</Type><ContainsText>true</ContainsText><ContainsData>true</ContainsData><ContainsBSS>true</ContainsBSS><PreserveUnusedSymbols>false</PreserveUnusedSymbols></ExtraMemoryDefinition></ExtraMemories>July 11, 2019 at 05:36 #25350
This error looks like you are using some special characters or variables in the linker script path and VisualGDB fails to resolve them (it would need to resolve the linker path in order to insert the memory definitions in it). We have added more detailed error message for this error in the following build: VisualGDB-22.214.171.12430.msiJuly 11, 2019 at 09:23 #25351
Thanks, now it’s clear. Problem was in BSP. We use our BSP, and *.ld files are located in project directories, so we use relative path.
“Additional memories” can’t work with relative path. May be this video can help: https://yadi.sk/i/AxoUnZe4IcFQYQJuly 14, 2019 at 23:41 #25367
Thanks for the update, we have reproduced the problem and fixed it in the following build: VisualGDB-126.96.36.19933.msiJuly 15, 2019 at 07:46 #25369
Now everything works fine. Thanks for your support.
You must be logged in to reply to this topic.