AM625: AM62x WKUP UART

Yu,

Thanks for your query , let me check the info you requested and get back to you about the issue resolution.

Regards

Anshu

Hi，any update here？

Yu, 

Please refer this thread to rebuild RTOS SDK SYSFW:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1206992/am625-using-wkup_uart0-from-cortex-a53-linux

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/08_06_00_18/exports/docs/api_guide_am62x/DEVELOP_AND_DEBUG_DMR5.html#autotoc_md184

Thanks for your reply.

I will test and let you know the results

Hi Yu,

If the use case is such that you are trying to run the UART R5_fss0-0 examples, then it cannot be done simply by importing into CCS. 

You will have to follow a couple of steps mentioned below: (Following is for UART Echo example)

1. Power Off the EVM
2. Connect the terminal to UART port in CCS.
3. Set the board in UART boot mode.
4. Power On EVM.
5. check for the logs, 'C' character will be coming in every 2-3 sec.
6. Disconnect the terminal from UART port in CCS.
7. Create appimage with the help of following command.
   1. cd ${SDK_INSTALL_PATH}
   2. gmake -s -C examples/drivers/uart/uart_echo/am62x-sk/r5fss0-0_freertos/ti-arm-clang

1. Go to the path "${SDK_INSTALL_PATH}/tools/boot/sbl_prebuilt/am62x-sk/default_sbl_null.cfg"
2. Change the path of appimage at line #31 with your appimage and save the changes. 
3. Open command prompt and run the below command
   cd ${SDK_INSTALL_PATH}/tools/boot
   python uart_uniflash.py -p COM<X> --cfg=sbl_prebuilt/am62x-sk/default_sbl_null.cfg (replace X with COM NO.)
4. After successful completion of above steps, Power Off the EVM.
5. Set the board in OSPI Boot Mode.
6. Connect the terminal to UART Ports in CCS.
7. Power On the EVM.
8. Input 8 characters in the UART Terminal.
9. See the logs coming on terminal connected to UART Ports in CCS.

You should be able to take input in the 3rd largest COM terminal, as mentioned in the screenshot below.

Let me know if this resonates with you.

Regards,

Vaibhav

Thanks for your reply, we can solve the problem by rebuilding

By the way, we also want to know whether TI has a git warehouse to maintain the DM Firmware source code? We want to do git version maintenance on this modification

Hi Yu,

yu chen said:

By the way, we also want to know whether TI has a git warehouse to maintain the DM Firmware source code? We want to do git version maintenance on this modification

I will check internally and let you know.

Regards,

Vaibhav

hi Yu,

we currently don't have public git repo for DM Firmware source code. source code is available as a part of SDK.

can you please elaborate your requirement

Regards

Anshu

Hi,

We have encountered some problems during the development process and need to consult:

1. We want to run the R5f case in mcu_sdk 8.06, but like M4F, the program does not run as expected after linking the R5F core loader after linux starts; how does TI load the R5F case based on CCS?

2. According to the above prompt information, we recompile the DM Firmware through the following command; we found that we did not make any changes, but recompiled the DM Firmware. After entering the Linux system, the communication between ipc_rpmsg_echo_linux and R5F failed. When using TI prebuilt DM Firmware, ipc_rpmsg_echo_linux and R5F communication is normal. Is our build DM Firmware command correct?
gmake -s -C examples\drivers\ipc\ipc_rpmsg_echo_linux\am62x-sk\r5fss0-0_freertos\ti-arm-clang clean PROFILE=release

gmake -s -C examples\drivers\ipc\ipc_rpmsg_echo_linux\am62x-sk\r5fss0-0_freertos\ti-arm-clang

Hi Yu,

I am assuming you are trying to run IPC Rpmsg Echo Linux example.

IPC is basically a multicore example, for this reason I would highly recommend you to have a look at the following FAQ https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1204069/faq-sitara-multicore-development-and-documentation

Regards,

Vaibhav