Hi Andrei,

Thanks for your kind response :) :)

1.Is your board flashed with the desired uboot? You can check by erasing the flash and then running lava, the desired uboot should be flashed on the board.

Ans. Using lava, i am unable to flash with u boot also. As you mention I have erased the flash up to 0 0x2000000 and tried again getting same issue.error_msg: Invalid job data: ["Invalid device configuration - missing 'commands'"].  

2. Can you lava-dispatcher machine reach the serial on the device?
Ans. In rza1h.jinja2, device-type file: i have added following commands to open serial console
{% set console_device = console_device|default("ttyACM0") %}
{% set baud_rate = baud_rate|default(115200) %}
{% set bootloader_prompt = bootloader_prompt|default("=>") %}

But i don't know lava-dispatcher machine reach the serial on the device or not. Due to job immediately terminated.
Manually i am able to flash through JLink with following commands :   JLinkExe -speed 15000 -if JTAG $JTAGCONF -device R7S721001 -CommanderScript load_spi_uboot.txt
load_spi_uboot.txt contains following:

rx 100
exec SetSkipProgOnCRCMatch=0

//
// Download application into QSPI flash
//

loadbin u-boot.bin,0x18000000
//verifybin u-boot.bin,0x18000000

exit


3. board_id: '{{ board_id|default('0000000000') }}',usb_vendor_id: '1366',usb_product_id: '0101' refers to JLink connected usb right. Can i change directly in the device-type .jinja2 file.

I am very thankful, if you can share your sample device jinja2 , device-type (jinja2 file) and working job description file.
I am just stuck with this issue issue.error_msg: Invalid job data: ["Invalid device configuration - missing 'commands'"] from last 5 day's. i gone through all the mail chain from lava-users but did not get proper information.Don't know how to debug this issue.
Your presence and input is more valuable for me .

I am attaching used job description and device& device-type .jinja files for your reference.

 

On Wed, May 20, 2020 at 4:04 PM Andrei Gansari <andrei.gansari@nxp.com> wrote:

Hello Nagendra,

 

Looks like error_msg: Invalid job data: ["Invalid device configuration - missing 'commands'"] is issued from serial.py so the validation reached executing serial commands.

 

1. Is your board flashed with the desired uboot? You can check by erasing the flash and then running lava, the desired uboot should be flashed on the board.
2. Can you lava-dispatcher machine reach the serial on the device?
3. Most likely it’s this pattern in job*.yaml it should look for the printed uboot header of prompt when the board is reset. The configuration below is used by Zephyr RTOS tests.

- test:

    monitors:

    - name: tests

      start: Running test suite common_test

      end: PROJECT EXECUTION SUCCESSFUL

      pattern: '(?P<result>(PASS|FAIL)) - (?P<test_case_id>.*)\.'

      fixupdict:

        PASS: pass

        FAIL: fail

 

Regards,

Andrei G.

 

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

 

Caution: EXT Email

Hi Andrei, Team,

 

Issue is solved this is because of lava-server & remote worker version mismatch. I tried to boot the DUT (RZA1_RSA , Renesas)  Using the rza1h.jinja2 file & job description with Segger Jlink debugger . I am getting following issue:

•  
• error_msg: Invalid job data: ["Invalid device configuration - missing 'commands'"]
• error_type: Job

I am looking forward for your kind response..

 

thanks

 

Regards

Nagendra S

  

 

On Tue, May 19, 2020 at 8:12 PM Nagendra Singamsetti <nag.singam91@gmail.com> wrote:

Hello Andrei , Team,

To get hands on knowledge, I have tried to boot Renesas images using JLink & Renesas - RZA1_RSA ver2 board on QSPI flash.

I took frdm-k64f.janja2 file as a reference created rza1h.jinja2 as a device-type. And added device as a renesas_worker1(DUT) under device-type rza1h. And connected to remote worker.

On Remote worker, Segger Jlink debugger is connected to the DUT with jtag cable.

 

But while submitting Job definition i am getting following error. 

 

 

Attaching Job files and device-type file for reference.

First time i am booting the hardware with Jlink using LAVA framework. Please help me out to debug this issue. 

 

Thanks 

 

Regards

Nagendra S

 

 

 

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

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