Smart way to debug Vybrid M4 Core only

[jochengerster]

Hi all,

we are currently working on a project, where we develop SW (based on eCos) for the M4 core only on Vybrid.

Every time we like to restart the SW we need to go through a long sequence, starting with Resetting the device (which leads to the M4 is in reset)

and bring the M4 again out of reset and load the elf file again.

We are using a Lauterbach Trace32 and ideally we would like to restart the M4 as simple as on a single core system.

Just loading the elf file again without a reset of the device leads to the application doesn't start probably.

Thanks for your help/ideas

best regards

Jochen

[jiri-b36968 · Accepted solution]

Hi Jochen,

/RESET signal will reset whole SoC (except RTC). So if you debug using Lauterbach put RESET command only in *.cmm file for CA5 core and do not use it in *.cmm file for CM4 core. You can just load new code for CM4 core and Lauterbach will set PC at beginning of your program. The only problem is that registers will not be in reset state. This have to handled at beginning of your CM4 core. Nevertheless most of the setting is usually done by CA5 code.

/Jiri