Hello,
I recently updated Ride7, RKit, and STVD on my laptop and now I'm having the following problems.
My problem is when using the STVD debugger. The development platform is win7 64. The tools are STVD 4.3.6, Raisonance Ride7 7.50.14.0185, RKit-STM8 2.54.14.0283. The debugger starts normally, no errors, it appears to be ready, when I set a breakpoint in the source code, I immediately get the following error message,
Die: DW_TAG_padding(abbrev=0, offset=0)
has children:FALSE
Error: Dwarf Error: Cannot find type of die
I have another development system (desktop), it is working properly, it is win8.1, the tools are STVD 4.3.2, Raisonance Ride7 7.42.12.0305, Rkit-STM8 2.48.12.0338. If I build the same project on the win8 platform and copy the .elf file to the win7 platform the debugger will work properly.
I did a binary file comparison on the two .elf files and it shows that the two files are not the same.
Also, the .aof files on the two platforms are different sizes (the working one is 30k smaller (1038k vs 1074k).
I've run ST Toolset.msi - no change.
I've removed all development tools, manually cleaned the registry, and reinstalled, and still have the same problem.
I would really like to update the development system on my desktop, but I don't want to take the chance of having both systems not working properly.
Any help would be greatly appreciated,
Thanks
Rick
Hello,
We would like to help you as quickly as possible on this issue, but we need to have more informations about the problem before we can help further.
In order to understand the issue you are facing, we need the following information about your configuration:
- Version of Windows: At a command prompt type the following command: "systeminfo.exe", which gives you a system report. We need the full "Operating System" and "Version" from the report.
- Version of Ride7 and RKit that you are using. You can get these from the Ride7 "Help | About" dialog box.
- Your Ride7 serial key or your RLink/Primer/Open4 serial number.
Please check from the Raisonance downloads page at http://support-raisonance.com that you are using the latest version of the tools.
Notes:
1) Raisonance toolsets and Ride7 operate on Windows 7 (32 and 64-bit), Windows Vista (32 and 64-bit) and Windows XP SP3 (32-bit only). Other versions of Windows, including Windows 2000, Windows XP 64-bit and Windows Server, are not supported.
2) Only native versions of Windows are supported. Emulators such as VMware, QEMU, Citrix, Wine, Xen (or others) are not supported.
Concerning your particular problem:
- Provide the steps you followed to raise the error.
- The precise error message you received, and which tool produced it. If possible, a screenshot of the message (using the PrtScr keyboard key) is helpful.
- Does the problem occur when using the examples given with Ride7 (from the Ride7 installation directory, default being "C:\Program Files\Raisonance\Ride\Examples\")?
Regards,
The Raisonance support team.
Thank you for responding to my post.
I will answer your questions in the order that they were asked.
- Version of Windows:
Host Name: ACER1
OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
- Version of Ride7 and RKit
Ride7 7.50.14.0185
RKit-STM8 2.54.14.0283
STVD 4.3.6
- Your Ride7 serial key or your RLink/Primer/Open4 serial number.
From the last emailed activation code.
With the serial number DongleEnterprise070E, you have requested the generation of an activation code for RKit-STM8 for the ACER1
computer.
Please put the following activation code in the license dialog box.
- Activation Code: 45AAFCB7-C208E47F-3ACB8110-D7B4344C
- Provide the steps you followed to raise the error.
(I don't know how to post a picture in this forum)
1) Run STVD from the START menu (as admin or not, it does not matter)
2) Select File --> Recent Workspaces --> project.stw
3) The project is loaded
4) Start the debug session by clicking on the Debug icon
5) Scroll down to main()
6) Set a breakpoint on a valid line of code
7) Immediately there is an error box that pops up that contains the following:
ST Visual Develop
Die: DW_TAG_padding(abbrev=0, offset=0)
has children:FALSE
Attributes:
Error: Dwarf Error: Cannot find type of die
8) The error can be cleared by clicking OK, but any further attempt to set a breakpoint results in the same error message
An alternate scenerio is:
1) Run STVD from the START menu (as admin or not, it does not matter)
2) Select File --> Recent Workspaces --> project.stw
3) The project is loaded
4) Set a breakpoint on a valid line of code in main()
5) Start the debug session by clicking on the Debug icon
6) Immediately there is a information box that pops up the contains the following:
ST Visual Develop
One or more breakpoints are not positioned on valid lines. Would you like to move these breakpoints to the next valid line?
7) Clicking Yes or No results in the breakpoint being removed, it is not moved. (I suspect this is because there is no debug
information)
If I scroll down to the end of the disassembly pane, I see the following:
0x8015 <?C?uchartol+9> 0x81 RET RET
0x8016 <?C?uchartol+10> 0x0000 NEG (0x00,SP)
NEG (ImAliveTime,SP)
has children: FALSE
attributes 0x0000 NEG (0x00,SP) NEG
(ImAliveTime,SP)
0x0000 NEG (0x00,SP) NEG (ImAliveTime,SP)
Error Dwarf Error: Cannot find type of die.
If I continue to move the slider in the disassebly pane, I see the following:
0x8bee
Error Dwarf Error: Cannot find referent at offset 8525.
- Does the problem occur when using the examples given with Ride7
Building and debugging the Towers.c example works when run from the Ride7 IDE.
Please let me know if there is anymore information that I can provide. I can provide screen shots if you will tell me how to post them.
Thanks,
Rick
Dear Rick,
Thank you for the feedback.
It seems to be an STVD issue, in this case you should ask directly ST microelectronic support.
In order to make some tests, could you provide us the name of the MCU you selected?
Are you using the Rlink debugger?
You can send the images to
Thanks
regards
Etienne,
The dubug tool that I am using is ST-LINK. I have RLink but have never had a reason to use it.
The MCU I am using is STM8S105C4.
I am sending you a PDF of a couple of error scenarios that may be of some help.
Thank you again for your help.
Rick
Dear Rick,
I'm sorry but I can't help you for this issue you should ask ST for STVD and ST-Link support.
Why you don't use the Rlink with Ride7? STM8S105C4 devices are well supported by our debugger, Ride7 and the Rkit-STM8 offer more functionality than STVD.
Could you try our products an let me know if you encounter some problems?
Best regards,
Etienne