Adding a new platform support for RA6M2 MCU in WICED

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
AbhiMin31
Level 1
Level 1
10 sign-ins 5 sign-ins First reply posted

We are trying to enable new platform support (RA6M2) on WICED with WIFI module. For this purpose, we have started with sample LED blinky application and created the appropriate make target to build for the new platform. Have proceeded with porting the few essential drivers and verified the build process; the binary .elf file is also generated (bypassed the bootloader compilation as of now).

When we tried to run or launch the program using Jlink debugger which is connected to our eval board, facing the below error with pop-up window saying,

This selection cannot be launched and there are no recent launches.

This error is observed only when we try the run the program in debug mode with no other errors. Can you share your comments or any inputs on this issue.

AbhiMin31_0-1646237278659.png


Thanks.

0 Likes
1 Solution
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Make sure that you've done the configurations under "GDB Segger J-Link Debugging".

Thanks

Aditi

View solution in original post

0 Likes
4 Replies
lock attach
Attachments are accessible only for community members.
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Please follow this document to configure the debug settings for JLink and check if that resolves the issue.

This document takes 43907 as a demo chipset but similar steps can be followed for setting the debug configurations as per your platform.

Thanks

Aditi

0 Likes

Re: Debugging Status result after using J link document_Attached steps.

We followed to make the connections with the Segger J-link as per mentioned in shared document and the J Link driver was changed to libusbK in the device manager using Zadig tool and also changed the configuration file mode flag(tools/OpenOCD/BCM4390x.cfg) and tried to build the new target for debugging using external JTAG with the make target as “ww101.02_blinkled-BLEWIT_REV2-debug JTAG=jlink download run” specific to our usecase. But evenafter following the steps, we were unable to detect the jlink43907 under debug launch configuration.

Expected Result:

AbhiMin31_0-1646832262785.jpeg

Obtained Result:

AbhiMin31_1-1646832301684.png

 

Thanks

Abinaya.

 

 

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Is the programming successful via Jlink? Can you try with a make target with -debug removed? Basically, is your application working in non-debug mode via Jlink?

Thanks

Aditi

 

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Make sure that you've done the configurations under "GDB Segger J-Link Debugging".

Thanks

Aditi

0 Likes