Hi Kumar, Andrei
From the previous lava- mailing list i have seen that you people addressed
jlink debugger information as like this :
*On Thu, Jan 23, 2020 at 7:33 PM Andrei Gansari <andrei.gansari at nxp.com https://lists.lavasoftware.org/mailman/listinfo/lava-users> *>>* wrote: *>>>>* From the screenshot it looks like you have a version of LAVA that does *>>* not support jlink boot method. *>>>>* JLink was added in version 2019.10-1*
- On Tue, Nov 26, 2019 at 2:36 PM Andrei Gansari <andrei.gansari at nxp.com https://lists.lavasoftware.org/mailman/listinfo/lava-users>
*>>* wrote: *>>>>* I’ve tested lava+jlink on Cortex M with both onboard debugger and *>>* external debugger, like the one you referenced. *>>>>* You should change the following if needed: *>>>>>>>>* address: *>>>>* *0x00000000* *>>>>* options: *>>>>* - '-device *MK64FN1M0xxx12'* *>>>>* - '-if SWD' *>>>>* - '-speed 4000'*
Can you please let me know, whether the latest lava version can support trace32 boot method instead jlink/cmsis-dac. trace32 debugger tool is designed by lauterbach and it is licensed one.
I am bit afraid whether this support is available from lava server or not as Jlink support added recently.
https://www2.lauterbach.com/pdf/app_t32start.pdf
We need trace32 debugger support as we are using cortex-M55 processor operations over here.
I am looking forward your kind support
thanks
Regards
Nagendra S