Forum Replies Created
-
AuthorPosts
-
YuriyParticipant
Hi,
In my case, the file name edp.xml and after removing BSPFilter debuging became work. Thanks
YuriyParticipantHi,
Thanks for reply!
I don’t have bsp.xml file according your path
Attachments:
You must be logged in to view attached files.YuriyParticipantNo, running VisualGDB.exe /about opens window “About VisualGDB”, but we can’t use GUI on our Jenkins. Command line only.
Is it possible to enter license key from console or from script, without opening windows?
YuriyParticipantNow everything works fine. Thanks for your support.
YuriyParticipantThanks, 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/AxoUnZe4IcFQYQ
YuriyParticipantThanks, 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: 5.4.110.3228
------------------ 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):
<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>
Attachments:
You must be logged in to view attached files.YuriyParticipantNo 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!
- This reply was modified 5 years, 4 months ago by Yuriy.
Attachments:
You must be logged in to view attached files.YuriyParticipantHi,
You are right, it can be done using GDB stub. Thanks for good advice! Now we have another question.
Now we use JLinkScript file, and have two options:
– rename file to Default.JLinkScript and place it into j-link directory C:\Program Files (x86)\SEGGER\JLink_V632d
– in VisualGDB Project Properties –> Debug settings –> Advanced settings –> Command line –> add argument -jlinkscriptfile C:\test_script.JLinkScriptBoth options are not suitable for us, because developers works not only with NXP RT1050 (so Default.JLinkScript shouldn’t be used for another MCUs), and absolute path to repository also different (we can’t specify relative path using -jlinkscript argument)
Our question: What is the right way to set JLinkScript file for only one project in the VisualStudio solution?
Useful links:
– Using J-Link Script Files – https://wiki.segger.com/Using_J-Link_Script_File
– J-Link / J-TraceUser Guide – https://www.segger.com/downloads/jlink/UM08001 (see 6.12 J-Link script files on p.172)YuriyParticipantHi! Marking these sections as NOLOAD solved problem, now .bin file has correct size. Thanks
YuriyParticipantHi!
I also have a problem with .bin file. Can I disable generating of this file? There are no option “Embedded Project” -> “Generate .bin file” in current VisualGDB version.
I enabled diagnostic MSBuild output via Tools->Options->Projects and Solutions -> Build and Run:
Target Performance Summary: 0 ms _SelectedFiles 1 calls 0 ms _SplitProjectReferencesByFileExistence 1 calls 0 ms SelectClCompile 1 calls 0 ms Build 1 calls ............ 547 ms Link 1 calls 603 ms ClCompile 1 calls 3403 ms GenerateBinFile 1 calls
I know, this happens because we are using external FLASH at address 0x60000000 and can’t specify offset for .bin file.
As result we got .bin file with size 1 611 264 460 bytes.On my SSD generating of bin file takes 3 seconds, but on standard HDD it takes tens of seconds!
In other projects generating of .bin file works fast enough. Have you a good solution for this problem?
YuriyParticipantHi! Build VisualGDB-5.4.9.2564 works fine, thanks for your support!
YuriyParticipantThanks, this approach looks good for us.
Actually, we use MSBuild and know this workaround. But what if Framework will change?
For example, in next update you will modify or add new source files to Framework. In such case we will need to update all our projects manually, and exclude Framework files from build again, right? How updater works?Thank you for support!
YuriyParticipantHi! I have checked my project with Fast Semihosting version 2.15, it works perfect. Thank you!
YuriyParticipantHi! Output from GDB has strange lines again:
Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061
What does it means? Is it problem of GDB, or Segger drivers, or our MCU firmware (wrong memory access or something like this)?
This message appears sometimes when I add new brekpoints, sometimes during debugging, sometimes after pause and step-by-step execution.
Full GDB log:
^running *running,thread-id="all" &"Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061\n" -break-delete 6 &"Quit (expect signal SIGINT when the program is resumed)\n" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "uxCurrentNumberOfTasks" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" 1006-interpreter-exec console flushregs ~"Register cache flushed.\n" &"Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061\n" 1006^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-select-frame 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" 1007-interpreter-exec console flushregs ~"Register cache flushed.\n" &"Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061\n" 1007^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "pxCurrentTCB->uxTCBNumber" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "uxCurrentNumberOfTasks" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" 1008-interpreter-exec console flushregs ~"Register cache flushed.\n" &"Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061\n" 1008^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -stack-list-frames 0 0 ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061" -data-evaluate-expression "\$pc" ^error,msg="Remote failure reply: E8DE072010270000D0470010F0260010010000000D0000002D240010A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5C8EE0720457003004E9B010000000061"
YuriyParticipantHi,
I measured time from request to response using external tools (oscilloscope). Response time increased when printf() to debug output is used.
Problem was in insufficient buffer space. There are no delays when output data fits into semihosting buffer. So first problem solved.
Second problem is in FastSemihosting option “When out of buffer space: Discard further data”.
I expected that data will be discarded, and no delays will occurs. But delays increased, and no output was discarded. What I do wrong?
Test project attached: buffer size 32 bytes, we write to semihosting directly 10 times by 1000 bytes.
Call stack: _write() –> WriteToFastSemihostingChannel() –> WriteRawFastSemihostingData() –> return 0;
Although we returned 0 from WriteRawFastSemihostingData(), function WriteToFastSemihostingChannel() can’t exit from loop untill data sent.
Thank you for your support!
Attachments:
You must be logged in to view attached files. -
AuthorPosts