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
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... 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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182670754&sdata=t%2Fkuf2RG5RJmbil521DTkfBG1x8rQKfD%2FY2RHeZ3oJw%3D&reserved=0>
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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182670754&sdata=t%2Fkuf2RG5RJmbil521DTkfBG1x8rQKfD%2FY2RHeZ3oJw%3D&reserved=0>
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.pdfhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182680760&sdata=P8gRMcoHdEYtIJh0rBPGGCiJLMjWvYBE51Wa%2FhHBZ7I%3D&reserved=0
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
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...
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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182670754&sdata=t%2Fkuf2RG5RJmbil521DTkfBG1x8rQKfD%2FY2RHeZ3oJw%3D&reserved=0>*
- 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182670754&sdata=t%2Fkuf2RG5RJmbil521DTkfBG1x8rQKfD%2FY2RHeZ3oJw%3D&reserved=0>*
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7C83245e67e70541a2a75208d7e8deda4e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637233916182680760&sdata=P8gRMcoHdEYtIJh0rBPGGCiJLMjWvYBE51Wa%2FhHBZ7I%3D&reserved=0
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
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.commailto: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...https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=2EBlgoAUGZYULCtk6ZPgDuxbHCwkJxtQ1hWlGVlPfOw%3D&reserved=0 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.orgmailto: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.orgmailto:kumar.gala@linaro.org>; andrei.gansari@linaro.orgmailto:andrei.gansari@linaro.org Cc: lava-users@lists.lavasoftware.orgmailto: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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=hoJcxN%2FR0hraPuZfR5Au6lZNV9sStC%2BiZstWlJZkb0w%3D&reserved=0>
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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=bIPkQb%2BK%2FrG%2FNKw%2BZrTDvN2TQw%2F9iG6%2FAWckROTthE4%3D&reserved=0>
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.pdfhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=ZlhsHczyMaQ35WIki4vlpYDTx3EUDu3UoBWgx7pSV4Q%3D&reserved=0
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
On Mon, 27 Apr 2020 at 12:58, 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
This is something we're trying to avoid. Could you try to use docker to host your tools in a container instead of a dispatcher? Docker support was released in 2020.04
milosz
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...
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
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Hi Andrei, Good Evening. Lava was installed in my machine with latest version 2020.04. And gone through your code. But i failed to find the following files :
*/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink-with-power.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/test_jlink.py*
*Is this Expected behavior???. or Am i missing something during installation*
And i am using *remote** worker* installed on one machine and lava-server is placed on other machine . Other tools like trace32 where i have to deploy ? lava-server or remote worker..
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... https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=2EBlgoAUGZYULCtk6ZPgDuxbHCwkJxtQ1hWlGVlPfOw%3D&reserved=0
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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=hoJcxN%2FR0hraPuZfR5Au6lZNV9sStC%2BiZstWlJZkb0w%3D&reserved=0>*
- 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=bIPkQb%2BK%2FrG%2FNKw%2BZrTDvN2TQw%2F9iG6%2FAWckROTthE4%3D&reserved=0>*
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=ZlhsHczyMaQ35WIki4vlpYDTx3EUDu3UoBWgx7pSV4Q%3D&reserved=0
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
Hello Nagendra,
Files were moved since I created the pull request. Please search them in the repository, I found jlink.yaml in /lava/tests/lava_dispatcher/pipeline_refs/jlink.yaml
You should use a docker container to install Trace32 as Milosz recommended, it should scale easy in the future. Trace32 should reside on lava-dispacher (remote worker in your case I think), this is how I’ve done it in an older version. The dispatcher it the component of Lava that actually interacts with the SW/HW you are testing.
Regards, Andrei
From: Nagendra Singamsetti nag.singam91@gmail.com Sent: Wednesday, April 29, 2020 3:46 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, Good Evening. Lava was installed in my machine with latest version 2020.04. And gone through your code. But i failed to find the following files : /usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink-with-power.yaml /usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink.yaml /usr/lib/python3/dist-packages/lava_dispatcher/tests/test_jlink.py
Is this Expected behavior???. or Am i missing something during installation
And i am using remote worker installed on one machine and lava-server is placed on other machine . Other tools like trace32 where i have to deploy ? lava-server or remote worker..
thanks
Regards Nagendra S
On Mon, Apr 27, 2020 at 5:28 PM Andrei Gansari <andrei.gansari@nxp.commailto:andrei.gansari@nxp.com> wrote: Please have a look at my pull requests:
https://git.lavasoftware.org/lava/lava/-/merge_requests/608/diffshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F608%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753232324&sdata=DbCqrTNe9XeaRQ5YucjgX7jKhRqmf6oq4FDcH9PMS14%3D&reserved=0 - script changes https://git.lavasoftware.org/lava/lava/-/merge_requests/758/diffshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F758%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753232324&sdata=l9zPYhbc5sWmzg5punUm7no83bF3wxJY1VTVYpHtW%2Bg%3D&reserved=0 - 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-LinkSoftwareAndDocumentationPackhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.segger.com%2Fdownloads%2Fjlink%2F%23J-LinkSoftwareAndDocumentationPack&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753242324&sdata=BgmF5f51V7qdXsffC9Fb7Zr5bmFQMGS8sEUFBlPetIA%3D&reserved=0
Regards, Andrei
From: Nagendra Singamsetti <nag.singam91@gmail.commailto:nag.singam91@gmail.com> Sent: Monday, April 27, 2020 12:42 PM To: Andrei Gansari <andrei.gansari@nxp.commailto:andrei.gansari@nxp.com> Cc: andrei.gansari@linaro.orgmailto:andrei.gansari@linaro.org; lava-users@lists.lavasoftware.orgmailto: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.commailto: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...https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753242324&sdata=mlujFkXkoXJEUbovaVeXehCqa961DBVlTIsWKXOBeNs%3D&reserved=0 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.orgmailto: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.orgmailto:kumar.gala@linaro.org>; andrei.gansari@linaro.orgmailto:andrei.gansari@linaro.org Cc: lava-users@lists.lavasoftware.orgmailto: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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753252315&sdata=zUxNz8te7PxW%2Fj%2Bl3agL8RvTQBL2cl4DQ4SuDxwYk1M%3D&reserved=0>
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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753252315&sdata=zUxNz8te7PxW%2Fj%2Bl3agL8RvTQBL2cl4DQ4SuDxwYk1M%3D&reserved=0>
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.pdfhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753262306&sdata=WtR8exMykShsePKDKO9P1NdjRgb8tLk1EPywML%2BW2Dg%3D&reserved=0
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
Hi Andrei,
Let say i want to boot MCU-target with J-link debugger. Below files must present on lava installation setup or these files are only for reference/test purpose.
/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink-with-power.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/test_jlink.py
YES , i found these files in repository , but not there after set-up LAVA from regular installation (sudo apt install lava).
Thanks Veera
On Wed, 29 Apr 2020 at 18:31, Andrei Gansari andrei.gansari@nxp.com wrote:
Hello Nagendra,
Files were moved since I created the pull request.
Please search them in the repository, I found jlink.yaml in * /lava/tests/lava_dispatcher/pipeline_refs/jlink.yaml*
You should use a docker container to install Trace32 as Milosz recommended, it should scale easy in the future.
Trace32 should reside on lava-dispacher (remote worker in your case I think), this is how I’ve done it in an older version.
The dispatcher it the component of Lava that actually interacts with the SW/HW you are testing.
Regards,
Andrei
*From:* Nagendra Singamsetti nag.singam91@gmail.com *Sent:* Wednesday, April 29, 2020 3:46 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,
Good Evening.
Lava was installed in my machine with latest version 2020.04. And gone through your code.
But i failed to find the following files :
*/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink-with-power.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/pipeline_refs/jlink.yaml
/usr/lib/python3/dist-packages/lava_dispatcher/tests/test_jlink.py*
*Is this Expected behavior???. or Am i missing something during installation*
And i am using *remote worker* installed on one machine and lava-server is placed on other machine .
Other tools like trace32 where i have to deploy ? lava-server or remote worker..
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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F608%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753232324&sdata=DbCqrTNe9XeaRQ5YucjgX7jKhRqmf6oq4FDcH9PMS14%3D&reserved=0
- script changes
https://git.lavasoftware.org/lava/lava/-/merge_requests/758/diffs https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F758%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753232324&sdata=l9zPYhbc5sWmzg5punUm7no83bF3wxJY1VTVYpHtW%2Bg%3D&reserved=0
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.segger.com%2Fdownloads%2Fjlink%2F%23J-LinkSoftwareAndDocumentationPack&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753242324&sdata=BgmF5f51V7qdXsffC9Fb7Zr5bmFQMGS8sEUFBlPetIA%3D&reserved=0
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... https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753242324&sdata=mlujFkXkoXJEUbovaVeXehCqa961DBVlTIsWKXOBeNs%3D&reserved=0
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* https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753252315&sdata=zUxNz8te7PxW%2Fj%2Bl3agL8RvTQBL2cl4DQ4SuDxwYk1M%3D&reserved=0*>*
- 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753252315&sdata=zUxNz8te7PxW%2Fj%2Bl3agL8RvTQBL2cl4DQ4SuDxwYk1M%3D&reserved=0*>*
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7C96e34730aafe426598ca08d7ec3b4996%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637237611753262306&sdata=WtR8exMykShsePKDKO9P1NdjRgb8tLk1EPywML%2BW2Dg%3D&reserved=0
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
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
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.
[image: renesas_jlink_job_error.png]
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... https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=2EBlgoAUGZYULCtk6ZPgDuxbHCwkJxtQ1hWlGVlPfOw%3D&reserved=0
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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=hoJcxN%2FR0hraPuZfR5Au6lZNV9sStC%2BiZstWlJZkb0w%3D&reserved=0>*
- 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=bIPkQb%2BK%2FrG%2FNKw%2BZrTDvN2TQw%2F9iG6%2FAWckROTthE4%3D&reserved=0>*
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=ZlhsHczyMaQ35WIki4vlpYDTx3EUDu3UoBWgx7pSV4Q%3D&reserved=0
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
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
[image: renesas_jlink_Invalid_device_configuration.png] 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.
[image: renesas_jlink_job_error.png]
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... https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=2EBlgoAUGZYULCtk6ZPgDuxbHCwkJxtQ1hWlGVlPfOw%3D&reserved=0
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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535647058&sdata=hoJcxN%2FR0hraPuZfR5Au6lZNV9sStC%2BiZstWlJZkb0w%3D&reserved=0>*
- 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=bIPkQb%2BK%2FrG%2FNKw%2BZrTDvN2TQw%2F9iG6%2FAWckROTthE4%3D&reserved=0>*
- 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 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7Ce85456035d9a41d1f45808d7ea8f4f13%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637235773535657054&sdata=ZlhsHczyMaQ35WIki4vlpYDTx3EUDu3UoBWgx7pSV4Q%3D&reserved=0
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
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 [renesas_jlink_Invalid_device_configuration.png] 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.commailto: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.
[renesas_jlink_job_error.png]
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.commailto:andrei.gansari@nxp.com> wrote: Please have a look at my pull requests:
https://git.lavasoftware.org/lava/lava/-/merge_requests/608/diffshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F608%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924598101&sdata=%2Fm92HFSnKkJ2hFCYf8auaE4JRD72%2BfHUXh4iPCsm4xw%3D&reserved=0 - script changes https://git.lavasoftware.org/lava/lava/-/merge_requests/758/diffshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavasoftware.org%2Flava%2Flava%2F-%2Fmerge_requests%2F758%2Fdiffs&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924608056&sdata=hAPMMG9Z1gO%2FTrjrTuL5D%2F9XQmuNnoJJ5VS4q9Drxa0%3D&reserved=0 - 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-LinkSoftwareAndDocumentationPackhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.segger.com%2Fdownloads%2Fjlink%2F%23J-LinkSoftwareAndDocumentationPack&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924608056&sdata=pNg1wTSf8uIjdvUsuVsDDCSI3%2Fn8bQlUHSeFTwqpo%2BY%3D&reserved=0
Regards, Andrei
From: Nagendra Singamsetti <nag.singam91@gmail.commailto:nag.singam91@gmail.com> Sent: Monday, April 27, 2020 12:42 PM To: Andrei Gansari <andrei.gansari@nxp.commailto:andrei.gansari@nxp.com> Cc: andrei.gansari@linaro.orgmailto:andrei.gansari@linaro.org; lava-users@lists.lavasoftware.orgmailto: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.commailto: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...https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F24883140%2Fcontrolling-trace32-via-command-line%2329424294&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924618015&sdata=VOGR0Q%2F%2FZFpV6h8kb%2FpVhdgb8Oj7ljAs2jkud1ln8VA%3D&reserved=0 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.orgmailto: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.orgmailto:kumar.gala@linaro.org>; andrei.gansari@linaro.orgmailto:andrei.gansari@linaro.org Cc: lava-users@lists.lavasoftware.orgmailto: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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924618015&sdata=ThEMClOcVHwcr7ta62gPfeR5j8QsANXBh86J5rDyNX8%3D&reserved=0>
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.comhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924627969&sdata=OvzksYvwTZZ5S76P04P9BmSPJFobIUb19zEXVZ%2F4%2FQA%3D&reserved=0>
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.pdfhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fapp_t32start.pdf&data=02%7C01%7Candrei.gansari%40nxp.com%7Cf168a54a55d04221e54608d7fc1646fb%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637255044924627969&sdata=cNsJlNfPS2EHtTO3%2BpvxLBoA4agJvLegyU%2Bp5qFE2h8%3D&reserved=0
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
lava-users@lists.lavasoftware.org
-
Andrei Gansari -
Milosz Wasilewski -
Nagendra Singamsetti -
veera brahmam