AM625: CSS Connect Target ：DDR not initialized with R5 connect

toby,

Can you please specify the steps you are doing for the verification of wakeup_uart. this will help us understand the flow and the issue much better

Regards

Anshu

I operated according to the following link completely. When loading Symbols, there was a prompt that needed to initialize DDR, and I followed the prompt to initialize the page that was always stuck in the screenshot above

I guess I couldn't test wkup_uart because I didn't successfully brush the shoe sbl with uniflash

software-dl.ti.com/.../DEVELOP_AND_DEBUG_DMR5.html ISABLE_LPM

Hi Toby,

This is my understanding of your problem. Your goal is to run the examples and test if the wkup_uart works.

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

Thank you very much. In fact, I have done the above steps in AM62X EVM and my own board, and EVM has been tested successfully. However, my board cannot use uniflash.py to burn mirror, and my own board will get stuck after sbl_uart_uniflash_stage2 after many attempts, as shown in the figure below

Hi Toby,

Error message says "XMODEM send failed.........". I am assuming this is happening because you might have missed out on installing few dependencies.

Please follow the steps here: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/08_06_00_18/exports/docs/api_guide_am62x/SDK_DOWNLOAD_PAGE.html#INSTALL_PYTHON3

For Windows: 

C:\> python -m pip install pyserial xmodem tqdm --proxy={your proxy server web-link and port}

For Linux: 

$ pip3 install pyserial xmodem tqdm --proxy={your proxy server web-link and port}

Regards,

Vaibhav

I don't think it's the xmodem and the dependencies, because the am62 evm can be successful in the same environment. The sbl_uart_uniflash_stage2 may be affected

Hi Toby,

I will look into this and get back to you.

Regards,
Vaibhav

Hi Toby,

I believe so there is a thread for this which is currently active and is handled by Prashant.

So, I would request you to watch this space((2) SK-AM62: After I wrote to emmc with uart_uniflash.py, I couldn't get into uboot from emmc. (spl_register_fat_device: fat register err - -1) - Processors forum - Processors - TI E2E support forums) for the answer.

Regards,

Vaibhav