st7 visual debug with st7mdt20-dvp3

[flavioantoniucci]

Posted on March 10, 2004 at 09:53

st7 visual debug with st7mdt20-dvp3

[flavioantoniucci]

Posted on March 10, 2004 at 06:09

software tool: st7visual debug rel. 2.5.4

hardware tool: st7mdt20-dvp3 teb rel 2-01

mainboard for st7-dvp3 rel 2-03

the informations showed in the ''about st7 visual debug'' window say:

(see also attached image)

gui component:

DVP3 vers. 1,4,3,0

core debugger:

GNUgdb 4.17,st7/smt7 ver 3.7.2

target:

gdi rev 126

master monitor rev 1.06

slave monitor rev st2

meb type 1

meb rev 2

meb max pld rev 3

meb acex pld rev9

teb type 1

teb rev 3

teb max pld rev 6

teb acex pld rev 4

we have the following problem working both with windows 2000 pro and windows 98 SE.

the software tool takes a long time (one minute ca) for entering in the debug mode from the editor.

it looks that it has some problem loading the ''GDI instrument interface''

once entered in the debugger the software loses the previous configuration and we have to open again the windows we work with

each time we get back to the editor from the debugger mode, the

time that the system takes, gets longer, it could take even 5 minutes

________________

Attachments :

aboutst7vdb.jpg : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006I04L&d=%2Fa%2F0X0000000bUP%2FKID1q_yQtVzLbe0TZjPSgL9mVXLtTi9Q6P_I8QO2ji0&asPdf=false

[shreya]

Posted on March 10, 2004 at 09:53

1/ Do you have too many breakpoints?

2/ In output window, right click to get contextual menu and make sure verbose is not selected.

Regarding problem of old debug ''window information'' being lost : Do you get an error saying ''Could not write to *.wdb''? This file should not be write protected.