Please have a look at my pull requests:

 

https://git.lavasoftware.org/lava/lava/-/merge_requests/608/diffs - script changes

https://git.lavasoftware.org/lava/lava/-/merge_requests/758/diffs - job sample

 

With JLink you need to install Segger’s software on the server where Lava dispatcher resides (in case you have multiple Lava servers).

https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack

 

 

Regards,

Andrei

 

From: Nagendra Singamsetti <nag.singam91@gmail.com>
Sent: Monday, April 27, 2020 12:42 PM
To: Andrei Gansari <andrei.gansari@nxp.com>
Cc: andrei.gansari@linaro.org; lava-users@lists.lavasoftware.org
Subject: Re: [EXT] [Lava-users] Test jobs to boot the targets through trace32

 

Caution: EXT Email

Hi Andrei,

 

Wonderful!!, 

Thanks for your time .. 

I need bit support from you, don't mine :) ,Can you please share your Jink scripts. I will use these as a reference will write comparable boot method for trace32 .

 

And if you can, Please share the appropriate Doc (link) to setup(interface) other software's in Lava server.  Setup Jlink with Lava server also fine. 

 

 

Regards

Nagendra S

 

On Mon, Apr 27, 2020 at 2:10 PM Andrei Gansari <andrei.gansari@nxp.com> wrote:

Hello Nagendra,

 

JLink was added as most NXP mcus use this interface, there is no support for T32 in Lava as far as I know.

Even if they use the same JTAG interface standard, Segger and Lauterbach use different hardware and software to interact.

I’ve used JLinkExe command line software (from Segger) to control the debugger, in the case of T32 you will probably need to use Lauterbach’s Trace32 command line software + scripts, such as: https://stackoverflow.com/questions/24883140/controlling-trace32-via-command-line#29424294

Haven’t used Trace32 GUI software for some years, never used the command line.

 

You can probably create a flashing script starting form JLink scripts, you need to:

• setup trace32 software on your Lava server
• learn how to use the command to flash your board using a cmm script
• change JLink scripts with T32 commands and cmm script generation
• pull request your changes so others can benefit 😊

 

Andrei Gansari

 

From: Lava-users <lava-users-bounces@lists.lavasoftware.org> On Behalf Of Nagendra Singamsetti
Sent: Saturday, April 25, 2020 9:05 AM
To: Kumar Gala <kumar.gala@linaro.org>; andrei.gansari@linaro.org
Cc: lava-users@lists.lavasoftware.org
Subject: [EXT] [Lava-users] Test jobs to boot the targets through trace32

 

Caution: EXT Email

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>

>> 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>

>> 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