TMDS64EVM: MCU flashing in SD Card BOOT Mode

Hi Raj,

From development perspective,

Raj Kumar said:

1. how can i access the miulti-core (4-R5 and 1-M4) at a time with mcu plus sdk?

You can use CCS to independently connect to the different cores.

Raj Kumar said:

2.how can i flash the code (without switching the boot mode ) into r5 , m4 cores and run the cores?

You can use CCS to load and run the examples.

Regards,

Prashant

hello Prashanth ,

I am trying to access the m4 core in A53. With the soft link command in  the directory    root@am64xx-evm:/lib/firmware#

Before that i have disabled all ipc notify in example.sysconfig, build it in ccs and .out i transferred into evm with the name led_blink_m4.out

After that i run the below commands

root@am64xx-evm:~# cp led_blink_m4.out /lib/firmware/pdk-ipc/ 

root@am64xx-evm:/lib/firmware# ln -sf /lib/firmware/pdk-ipc/led_blink_m4.out  am64-mcu-m4f0_0-fw 

with above process i can able to achieve the led blinking.(access the m4 core in A53 and flash m4)

i followed same steps for R5-0_0 core also but i can't able to access the r5 core in A53(i am making the r5 gpio high and low in while(1) with delay)

And i try to flash the code via ccs it is showing the error as mentioned in below 

Error connecting to the target:
(Error -2062 @ 0x0)
Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 12.6.0.00029) 

i restarted the entire system and tried but same issue.

flashing the mcu cores in sd card boot mode and run is my priority.

Hello Nick ,

we are using the Debian Rt Os  and mcu+sdk version 09.01.00 

i followed above thread for booting the remote cores. But after that i try to start and stop the remote core by sysfs interface (echo to the remotecor1/state file) i am getting Error 22 which relates to the invalid parameter in linux so that i can't able to boot and run the code in linux.

i am attaching that particular screenshot with this post.

Thanks you !

Hello Raj, 

Linux error code 22 usually means that you did not include a resource table in your remote core binary. Please follow the links I gave you in my previous response.

Regards,

Nick

Hello Nick,

I am following the above link that you are provided ,

i was modified the example.sysconfig,since i included the linux ipc i should update the linker.cmd file.

i am following below link  to apply git patch   https://dev.ti.com/tirex/explore/content/am64x_academy_9_00_00_00_v2/_build_am64x_academy_9_00_00_00_v2/source/multicore/other-resources/apply-git-patch.html#dev-apply-git-patch

My board is TMDS64-evm but it is showing am64-sk /............/.cmd not found

 it is showing error in my linux pc which is ubuntu 18.04 and i am attaching the screenshot with the post

how to fix this issue?

thankyou,

r

Hello Raj,

As described in my first reply, there were some differences between SDK 9.0 and SDK 9.1, including the fact that the memory configurator tool is used by default for memory allocation. So you will not be able to simply apply the git patches to linker.cmd files, since there are not linker.cmd files by default in SDK 9.1 (instead, the linker.cmd files are generated during make).

Please see that link I pointed to above:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1323865/sk-am64b-syscfg-ti_drivers_config-o-build-errors-while-trying-to-build-led-blink-example-with-ipc/5036614#5036614

You'll need to manually make the changes you see in the patch file in the SysConfig tool.

I apologize for the confusion, but it will probably take me a couple more weeks before I am able to update the academy modules for SDK 9.1.

Also heads-up, I am about to go on vacation for a while. I will probably be unable to give much in the way of replies until April.

Regards,

Nick