[WalterF]

I created a ticket and sent gdbsettings to you.

[WalterF]

Thanks for your hint! I got a custom version of VisualGDB.
Use custom GDB executable: When I select gdb on deploy machine it will be ignored and always changed to build machine.

Compiling does not work with different SSH build and deploy computers. Log tells that msbuild-mak will be startet on local computer.

By the way: When start VisualGDB Project properties ‘Computer used for building and debugging’ always shows (local computer). I have to change to MSBuild settings and switch back to Project settings in order to get the correct IP and SSH shown.

[WalterF]

Hi,

you are right. It depends on the name and it was a conflict with an ARM NEON register name (d2).
double d2 = 1.125;
double dV2 = 1.125;
d2 shows wrong value (interpreted as builtin_type_ieee_double), dV2 ist correct (interpreted as double).

• This reply was modified 7 years, 11 months ago by WalterF.

[WalterF]

Adding the picture did not work.

The Tooltip shows 3.05866665335518889e+154 instead of 28.4375 which is correctly displayed in the local variables window.

 

[WalterF]

Hi Magic

C:\Users\yourname\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp
GDBStartupCommands
Here I added the commands for memory controller init. F.e.:
set {int}0x30340004 = 0x0F400005
set mem inaccessible-by-default on

just before
$$com.sysprogs.jlink.program$$

Greetings

• This reply was modified 7 years, 11 months ago by WalterF.

[WalterF]

Thank you for you fast answer and proposal.

If I am really the only person with uninitialized DDR RAM I can live with this. Only after your next update I need not to forget to change edp.xml again.

At moment I’m happy with the situation because I am able to debug and work;-)

[Author]

Posts