AM2431: Connecting to AM2431 via debugger

Hi Dominik,

Can you share what platform you are using, AM243x EVM, AM243 LP, or custom board (ALV or ALX, GP device or HS-FS device)?

Best regards,

Ming

Hi Ming,
I am using custom AM2431 custom board, ALX variant and GP.

BR

Dominik

Hi Dominik,

What is the required SKD, CCS and sysconfig version for AM2431_ALX?

[MW] The CCS and syscfg version are closely related to the MCU+ SDK version. They are stated in the MCU-PLUS-SDK-AM243X Software development kit (SDK) | TI.com. The CCS 12.1.0 and the syscfg 1.14.0_2667 and TI ARM CLANG 2.1.2 LTS are used for MCU+ SDK 08.05.00.34 (latest) 

When creating target configuration for AM2431_ALX. Do I need to do anything else than selecting the AM24x.gel file for M3 core?

[MW] You can try the AM243x_LAUNCHPAD instead, since the AM243x LP is using the AM243x_ALX SoC

Is the procedure for connecting to device different on AM2431 different then the one I have described above?

[MW] The preferred way to initialize the SoC is to use the SBL_NULL. Please refer to the following URL for details: AM243x MCU+ SDK: EVM Setup (ti.com)

Best regards,

Ming

Hello Ming,

let me clarify what are my issues.

I have a custom am2431_ALX board with custom flash. This means that I cannot use SBL null at the moment.
To make a flash driver and test it out I need to initialize the device via CCS scripting console by running:

loadJSFile "C:/ti/mcu_plus_sdk_{soc}_{sdk version}/tools/ccs_load/am243x/load_dmsc.js"

I was able to do this on custom am2434 board with no problems, but now we have switched to am2431

I have copied the required setup in SDK v8.5. And created a target configuration. I have tried AM2434_ALX,
AM243x_LAUNCHPAD and AM2431_ALX (Only available in CCS 12.2, in other test I have used the 12.1).
In all configurations I have put emulation\gel\AM24x\AM24x.gel file as initialization script for M3 core.
When I launch this configuration and put load_dmsc.js initialization script into scripting console. I recieve this error:
(Error -1170 @ 0x0) Unable to access the DAP. Reset the device....

Is this a possibility to initialize am2431 via scripting console ?
Are there any steps for creating configuration that I have skipped?/Could you share a working am2431 configuration?

Thanks for your time and have a great day.

Dominik Ondra

Hello Ming,

I have tried both "UART" and "NO boot" modes which previously worked with the load_dmsc.js initialization.
This produces the same error as mentioned above. 

Can you confirm that the only thing that i need to do when creating the AM2431_ALX target configuration is to select correct device, set xd110 debugger power selection and set initialization on M3 core to  emulation\gel\AM24x\AM24x.gel ?

Do you have any tips on how to troubleshoot this?

Thanks for your help,

Dominik

Hi Dominik,

I never used the AM2431_ALX target configuration with the loaddsmc.js, but I know for sure the AM243x_LAUNCHPAD works well with the load_dmsc.js for AM243x_ALX.

You can check the target configuration difference between the AM243x_LAUNCHPAD and the AM2431_ALX. I think the only difference should be the gel files for R5F_0_0 and DMSC (M3)

"I was able to do this on custom am2434 board with no problems, but now we have switched to am2431"

Which target configuration worked for your AM2434 custom board before? The AM2434 SoC you used is ALX or ALV?

Have you tried the "NO Boot" mode, launch the AM243x_LAUNCHPAD target configuration, then connect to the R5F_0_0 using JTAG? 

Best regards,

Ming

Hi Ming,

for AM2434 board I have created target configuration with the steps described above 

Dominik Ondra said:

Can you confirm that the only thing that i need to do when creating the AM2431_ALX target configuration is to select correct device, set xd110 debugger power selection and set initialization on M3 core to  emulation\gel\AM24x\AM24x.gel ?

This was created because, the launchpad configuration (created as described in the SDK guide) did not work. My guess is the initialization script gels for R5F_0_0 are different. I was under the impression, that creating the same configuration, but changing the device type would be enough.

Both AM2434/1 devices are ALX variant.

Yes, I have tried all available ALX/LaunchPad device options in NO boot and UART boot mode.

Do you have acess to any target configuration, which has worked with AM2431 and load_dmsc.js ?

Best regards,

Dominik

Hello Ming

this solved my Issue, I wasnt aware of the B variant hsfs requirement.

Thanks for your help.