AM2434: am2434

To develop multicore application, please get started by referring this: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1394609/faq-processor-sdk-am64x-how-to-do-ipc-communication-with-only-two-cores-say-r5fss0-0-and-r5fss1-1?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

Hi Baruch,

Baruch Einziger said:

You didn’t answer my previous question, but I was able to resolve those issues on my own and now my multicore application is running correctly.

The example which you mentioned has not being given out for AM243-LP as you also mentioned, but you could take a reference from here:

https://github.com/TexasInstruments/mcupsdk-core/tree/next/examples/drivers/boot/sbl_qspi_multicore_elf

Baruch Einziger said:

Do you want me to also add a reference to the empty sbl_qspi_multicore_elf directory in SDK 10.01.00 (like you mentioned earlier today), so TI understands what’s missing from their SDK?

Please share this, thank you.

Baruch Einziger said:

Here is my current attempt using MulticoreImageGen.exe with a batch file:

cd C:\am2434\tools MulticoreImageGen LE AM2434 app_multi_core.appimage ^ agg_main_r5fss0-0_freertos_ti-arm-clang1.rprc ^ agg_r5fss0-1_nortos_ti-arm-clang.rprc ^ agg_m4fss0-0_nortos_ti-arm-clang.rprc

Are you referring the command mentioned in the MCU+ SDK? https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/TOOLS_BOOT.html#MULTICOREIMAGEGEN_TOOL

Looking forward to your response.

Best,

Vaibhav

Dear Vaibhav,

Your answer based on SDK 11 was very helpful, but I encountered a small limitation related to file name length. The process worked once I shortened the file names.

My next challenge is browsing the XIP image in the UniFlash utility. In my project, there is no system-level XIP file, so I used the XIP file generated from R00. It appeared that the tool successfully programmed the QSPI flash, but afterwards the board stopped functioning correctly. I can no longer load any program onto my AM243X-LP.

I tried changing the boot mode and attempted to erase the QSPI flash using UniFlash, but the issue persists. Could you please advise:

1. How I can restore my evaluation board to a working state?

2. What are the correct parameters for programming an XIP image with UniFlash?

Thank you for your support.

Best regards,
Baruch

Hi Baruch,

Baruch Einziger said:

file name length

Was it something to do with MSRAM for AM243-LP vs AM243-EVM?

Baruch Einziger said:

How I can restore my evaluation board to a working state?

I believe erasing the flash will solve the issue, so that you can reprogram later on.

Can you please try the following steps:

• Instead of using the UNIFLASH GUI Tool(if you were using) use the python script and flash using default sbl null
• Default sbl null will have uart uniflash which will flash the sbl null and that should be it.
• Modify the cfg file as follows and then do the flashing:
  

Put the size as the flash size and rest should be okay.

Regards,

Vaibhav

Subject: Issue after Flash Erase on AM243x-LP

Dear Vaibhav,

I erased the flash on my AM243x-LP. First, I ran uart_uniflash_gui.py, but I was not sure how to activate it as you suggested. After that process, the UniFlash tool erased the entire flash.

Following the erase, I was able to load a program to R00 and R01, but the M4 core failed. I tried working without the M4 core, but after subsequent power cycles or reloads in CCS, I returned to the original problem. I’ve added both error messages below for your reference.

First CCS error message:

After erasing the flash, this solution was not stable. When I tried again with AM243x-LP reset, power-on, or reactivating CCS, the error changed to:

Second CCS error message:

Could you please advise how I can resolve this issue and ensure stable operation after erasing the flash?

Best regards,
Baruch

Dear Baruch,

Baruch Einziger said:

uart_uniflash_gui.py

Instead of using this, can you try with uart_uniflash.py for several cycles and let me know the results.

Best Regards,

Vaibhav

Hi Baruch,

Vaibhav Kumar said:

Modify the cfg file as follows and then do the flashing:

Instead of writing it in the command itself, try writing it this way in the default_sbl_null.cfg file and running the script as mentioned here.

Link: software-dl.ti.com/.../EVM_SETUP_PAGE.html

Thanks,

Vaibhav

Dear Vaibhav,

I made the changes but the error message remained the same.

C:\tools_am2434\python>Python uart_uniflash.py -p COM7 --file=sbl_null.release.hs_fs.tiimage --operation=flash --flash-offset=0x0 --erase-size=0x4000000
Traceback (most recent call last):
File "C:\tools_am2434\python\uart_uniflash.py", line 770, in <module>
main(sys.argv[1:])
File "C:\tools_am2434\python\uart_uniflash.py", line 518, in main
elif linecfg.optype in ["flash-mcelf-xip"]:
^^^^^^^
UnboundLocalError: cannot access local variable 'linecfg' where it is not associated with a value

thanks

Baruch

Dear Baruch,

This is a script error.

To avoid this, please use the following command as mentioned in the link shared above:

Also note, in the file, default_sbl_null.cfg, make the following change by adding the line in between for erasing flash

Looking forward to the results.

Thank you,

Vaibhav

Dear Vaibhav,

I ran the uart_uniflash.py script after copying the default_sbl_null.cfg file into my directory. I also copied the files sbl_uart.release.hs_fs.tiimage and sbl_null.release.hs_fs.tiimage, shortened their names, and updated the default_sbl_null.cfg file to use these modified filenames. The process completed without any errors.

However, when I tried to activate my project (as I did before attempting to burn the flash), the R00 and R01 cores connected successfully, but the M4 core still showed a memory issue. After exiting and restarting CCS, I was no longer able to load my program—it now fails at core R00.

At this stage, I am still unable to burn my program to flash, and my AM243X-LP appears to be in a fault state. Could you please advise how I can resolve this issue? For software development, I can consider purchasing a new board, but I am mainly concerned about ensuring that the system can boot and run from flash after power-on.

Thank you for your support.

Best regards,
Baruch

Hi Baruch,

Baruch Einziger said:

the R00 and R01 cores connected successfully, but the M4 core still showed a memory issue

Just to clarify, I am assuming that the R50 and R51 is a multicore application and M4 is a standalone application.

And that you are loading them via CCS loading by connecting to the core and loading the .out

You observed the following behaviour:

1. After flashing default_sbl_null.cfg successfully.
2. You loaded R50 and R51 successfully but M4 core shows memory issue.
3. The second time you tried, not even able to load R50 application.

Regards,

Vaibhav

Dear Vaibhav

That's exactly what happened. Before burning the software, I would load the three cores one after the other using CCS.

Regards,

baruch

Hi Baruch,

Baruch Einziger said:

That's exactly what happened. Before burning the software, I would load the three cores one after the other using CCS.

I can try doing the same, and update you in sometime.

Thanks,

Vaibhav

Hi Baruch,

Baruch Einziger said:

but the M4 core still showed a memory issue

Does this match with what is shown in the following threads?

•  MCU-PLUS-SDK-AM243X: My M4 core doesn't like the CCS build process 
•  TMDS64EVM: Data verification error M4F 

Also, I tried loading R500 and M400 on CCS and ran into no issues. Will also try loading the R501 application.

Regards,

Vaibhav

Dear Vaibhav,

I believe you have successfully managed to burn your EVB. In my case, however, I may have made a mistake during the burning process. Without fully understanding what happened to my AM243X-LP, it is difficult for me to continue development.

It is, of course, easy to purchase a new AM243X-LP, but my main concern is understanding how my current board could have been damaged while using UniFlash. The tool correctly recognized my evaluation board when I attempted to burn the QSPI external flash, yet the board no longer seems to function as expected.

Could you please provide guidance on what might have gone wrong, and how I can recover or prevent this issue in the future?

Thank you for your support.

Best regards,
Baruch

Dear Baruch,

Thanks for elaborating your problem.

When you say board has gone bad, I am assuming you meant to say QSPI Flash has gone bad.

Also please note the following:

I would suggest using the script itself using python command paired up with uart_uniflash.py.

I will provide further inputs in sometime.

Best Regards,

Vaibhav

Dear Vaibhav,

As I mentioned earlier, immediately after erasing the QSPI flash using uart_uniflash.py, I encountered serious issues when trying to reload my project through CCS.

• First attempt (right after erase):
  When I tried to load my project, the M4 core failed to connect.

• Second attempt (after reset):
  I could no longer load my project—or any other project at all.

Details from CCS console:

• Flash erase was performed with uart_uniflash.py.

• First load attempt of the original project:

  MAIN_Cortex_R5_0_0: AM2434_ALX MAIN_Cortex_R5_0_0: GEL Output: CPU reset (soft reset) has been issued through GEL. MAIN_Cortex_R5_0_1: AM2434_ALX MAIN_Cortex_R5_0_1: GEL Output: CPU reset (soft reset) has been issued through GEL. BLAZAR_Cortex_M4F_0: Error connecting to the target: (Error -1274 @ 0x0) Error encountered during connect sequence. Possible reasons: inaccessible Core/logic due to Power, Clocks, or Security Authentication.

• Next attempt (after reset):

  MAIN_Cortex_R5_0_0: AM2434_ALX MAIN_Cortex_R5_0_0: GEL Output: CPU reset (soft reset) has been issued through GEL. MAIN_Cortex_R5_0_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x40: (Error -1065 @ 0x40) Unable to access device memory. Suggestion: Verify memory address, confirm configuration, power-cycle board, or try more reliable JTAG settings (lower TCLK). File Loader: Verification failed: Target failed to write 0x00000000 Load failed: agg_main_r5fss0-0_freertos_ti-arm-clang1.out

At this stage, I am unable to load any project onto the AM2434-LP board after erasing the flash.

Could you please advise how to recover the board and restore the ability to load applications through CCS?

Best regards,
Baruch

Hi Vaibhav,

I successfully restored one AM243x-LP on my first try, but I’m trying to run the same procedure on a second board with the same initial errors and I’m running into a file reference issue.

My batch flow fails because default_sbl_ospi.cfg (line 30) references:

I can’t find this file anywhere in MCU+ SDK AM243x 10.01.00.32. On the earlier attempt, even though I hit this reference problem, the first board ended up restored; however, I can’t complete the restore on the second board now.

Could you please advise:

1. Which example/appimage should be used with default_sbl_ospi.cfg for SDK 10.01.00.32?

2. If that file was renamed or moved in this SDK, what’s the correct replacement path/filename?

3. If there’s an updated default_sbl_ospi.cfg, where can I get it?

Thanks in advance for your help!

Best regards,
Baruch

Hi Baruch,

For the file which you mentioned you are not able to find.

You can find that in the following directory: C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\system_freertos_nortos

You might need to build the application as mentioned above in the directory or it might have come already built with the MCU+ SDK you are using.

Just run gmake PROFILE=release at the directory I have mentioned.

Hope this helps.

Thanks,

Vaibhav

Dear Vaibhav,

I tried following the steps you suggested, but the process ended with an error. The file ipc_notify_echo_system.release.appimage_xip was not generated.

I imported the project into my directory, built it with all the cores, and generated the release version. However, this file still did not appear in my project.

Could you please let me know your thoughts? I still have no clear understanding of why UniFlash causes my LP-AM243x-LP to stop working, and how it recovers when the procedure—which should normally fail—manages to write once and restore my EBV.

Thanks,
Baruch

Here is the example output from my run:

Hi Baruch,

Can you open the imports.mak file.

Here please check if the CCS and the SysConfig version mentioned is installed in your C:\ti\ directory or not.

Looking forward to your response.

Thanks,

Vaibhav 

Dear Vaibhav

I can’t find the file imports.mak

I was looking at project properties CCS General Products my sysconfig is 1.22.0 and my sdk 10.1.0.32.

I am using ccs version    12.8.0.202407141830

All the tools install in my  c:\ti.

Best regardes

baruch

Baruch Einziger said:

I can’t find the file imports.mak

This is a top level file in the MCU+ SDK. Please recheck and check the versions as mentioned here.

Vaibhav Kumar said:

Here please check if the CCS and the SysConfig version mentioned is installed in your C:\ti\ directory or not.

hi Viabhav

i find the file imports.mak.

there is a conflict. i assume from my project that i used sysconfig 1.22.0. The sysconfig version in the imports.mak is 1.21.2.

i have both installation on my c:\ti

please tell me what to do,

thanks 

baruch

Hi Baruch,

Please update the imports.mak file with the CCS and SysConfig version you are using. Basically give the correct paths to the installed version on your system.

Please build it then and let me know if it is successful.

Thanks,

Vaibhav

Hi Vaibhav

I made an update to the imports.mak file to point to SysConfig version 1.22.0 and then re-ran the make process in the location you recommended. Unfortunately, the behavior did not change — I am still seeing the same error, and the file ipc_notify_echo_system.release.appimage_xip is still missing.

Below are the detailed results from the batch file execution:

C:\tools_am2434\python>update1

C:\tools_am2434\python>cd C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\system_freertos_nortos

C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\system_freertos_nortos>C:\ti\ccs1281\ccs\utils\bin\gmake PROFILE=release

Generating SysConfig files ...

C:/ti/sysconfig_1.21.2/nodejs/node C:/ti/sysconfig_1.21.2/dist/cli.js --product C:/ti/mcu_plus_sdk_am243x_10_01_00_32/.metadata/product.json --script ../m4fss0-0_nortos/example.syscfg --context m4fss0-0 --output ../m4fss0-0_nortos/ti-arm-clang/generated --script ../r5fss1-1_nortos/example.syscfg --context r5fss1-1 --output ../r5fss1-1_nortos/ti-arm-clang/generated --script ../r5fss1-0_nortos/example.syscfg --context r5fss1-0 --output ../r5fss1-0_nortos/ti-arm-clang/generated --script ../r5fss0-1_nortos/example.syscfg --context r5fss0-1 --output ../r5fss0-1_nortos/ti-arm-clang/generated --script ../r5fss0-0_freertos/example.syscfg --context r5fss0-0 --output ../r5fss0-0_freertos/ti-arm-clang/generated

Warning: SysConfig has been updated to use standard TI part numbers. The device AM2434 has been automatically selected. If this is not the desired please open SysConfig to change it.

Running script...

Validating...

info: r5fss0-0 CONFIG_MPU_REGION0(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-0 CONFIG_MPU_REGION1(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-0 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) attributes: Some memory region(s) within this range is Shared among cores.

info: r5fss0-0 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-0 CONFIG_MPU_REGION5(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-0 /kernel/dpl/debug_log uartLog.baudRate: Actual Baudrate Possible: 115385 (0 % error)

info: r5fss0-1 CONFIG_MPU_REGION0(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-1 CONFIG_MPU_REGION1(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-1 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) attributes: Some memory region(s) within this range is Shared among cores.

info: r5fss0-1 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss0-1 CONFIG_MPU_REGION5(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-0 CONFIG_MPU_REGION0(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-0 CONFIG_MPU_REGION1(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-0 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) attributes: Some memory region(s) within this range is Shared among cores.

info: r5fss1-0 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-0 CONFIG_MPU_REGION5(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-1 CONFIG_MPU_REGION0(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-1 CONFIG_MPU_REGION1(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-1 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) attributes: Some memory region(s) within this range is Shared among cores.

info: r5fss1-1 CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: r5fss1-1 CONFIG_MPU_REGION5(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

info: m4fss0-0 CONFIG_MPU_REGION0(/kernel/dpl/mpu_armv7) $name: This MPU region includes other cores' memory regions as well. Pl. make sure what you configure.

Generating Code (example.syscfg)...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_dpl_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_dpl_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_drivers_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_drivers_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_drivers_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_drivers_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_pinmux_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_power_clock_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_board_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_board_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_board_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_board_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_soc.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_lwipif.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\ti_enet_lwipif.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\linker.cmd...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-0_freertos\ti-arm-clang\generated\linker_defines.h...

Generating Code (example.syscfg)...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_dpl_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_dpl_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_drivers_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_drivers_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_drivers_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_drivers_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_pinmux_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_power_clock_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_board_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_board_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_board_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_board_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_soc.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_lwipif.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\ti_enet_lwipif.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\linker.cmd...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss0-1_nortos\ti-arm-clang\generated\linker_defines.h...

Generating Code (example.syscfg)...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_dpl_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_dpl_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_drivers_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_drivers_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_drivers_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_drivers_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_pinmux_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_power_clock_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_board_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_board_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_board_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_board_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_soc.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_lwipif.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\ti_enet_lwipif.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\linker.cmd...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-0_nortos\ti-arm-clang\generated\linker_defines.h...

Generating Code (example.syscfg)...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_dpl_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_dpl_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_drivers_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_drivers_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_drivers_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_drivers_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_pinmux_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_power_clock_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_board_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_board_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_board_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_board_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_soc.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_lwipif.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\ti_enet_lwipif.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\linker.cmd...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\r5fss1-1_nortos\ti-arm-clang\generated\linker_defines.h...

Generating Code (example.syscfg)...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_dpl_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_dpl_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_drivers_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_drivers_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_drivers_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_drivers_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_pinmux_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_power_clock_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_board_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_board_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_board_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_board_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_config.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_config.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_open_close.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_open_close.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_soc.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_lwipif.c...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\ti_enet_lwipif.h...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\linker.cmd...

Unchanged C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\m4fss0-0_nortos\ti-arm-clang\generated\linker_defines.h...

C:/ti/ccs1281/ccs/utils/bin/gmake -C ../r5fss0-0_freertos/ti-arm-clang/ all SYSTEM_FLAG=true

gmake[1]: Entering directory 'C:/ti/mcu_plus_sdk_am243x_10_01_00_32/examples/drivers/ipc/ipc_notify_echo/am243x-lp/r5fss0-0_freertos/ti-arm-clang'

C:/ti/ccs1281/ccs/utils/cygwin/mkdir -p obj/release/

 Compiling: am243x:r5fss0-0:freertos:ti-arm-clang ipc_notify_echo.release.out: ../../../ipc_notify_echo.c

C:/ti/ti-cgt-armllvm_4.0.1.LTS/bin/tiarmclang -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mthumb -Wall -Werror -g -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function  -Os  -IC:/ti/ti-cgt-armllvm_4.0.1.LTS/include/c -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/FreeRTOS-Kernel/include -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/portable/TI_ARM_CLANG/ARM_CR5F -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/config/am243x/r5f -Igenerated   -DSOC_AM243X   -MMD -o obj/release//ipc_notify_echo.obj ../../../ipc_notify_echo.c

process_begin: CreateProcess(NULL, C:/ti/ti-cgt-armllvm_4.0.1.LTS/bin/tiarmclang -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mthumb -Wall -Werror -g -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -Os -IC:/ti/ti-cgt-armllvm_4.0.1.LTS/include/c -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/FreeRTOS-Kernel/include -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/portable/TI_ARM_CLANG/ARM_CR5F -IC:/ti/mcu_plus_sdk_am243x_10_01_00_32/source/kernel/freertos/config/am243x/r5f -Igenerated -DSOC_AM243X -MMD -o obj/release//ipc_notify_echo.obj ../../../ipc_notify_echo.c, ...) failed.

make (e=2): The system cannot find the file specified.

makefile:159: recipe for target 'ipc_notify_echo.obj' failed

gmake[1]: *** [ipc_notify_echo.obj] Error 2

gmake[1]: Leaving directory 'C:/ti/mcu_plus_sdk_am243x_10_01_00_32/examples/drivers/ipc/ipc_notify_echo/am243x-lp/r5fss0-0_freertos/ti-arm-clang'

makefile:47: recipe for target 'corebuild' failed

gmake: *** [corebuild] Error 2

C:\ti\mcu_plus_sdk_am243x_10_01_00_32\examples\drivers\ipc\ipc_notify_echo\am243x-lp\system_freertos_nortos>