This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM62P: No able to configure ethernet using MCU

Part Number: AM62P
Other Parts Discussed in Thread: UNIFLASH

I am trying to run UDP with the help of MCU R5 on the board, i am following the  MCU+SDK guide and i have successfully ran the Hello world program,for the start i am using the prebuilt example and for that i am following https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/12_00_00_27/exports/docs/api_guide_am62px/EXAMPLES_ENET_LWIP_CPSW.html but i am not able to get the output show in the end infact i am not able to get anything on the CCS console, i am only getting this as output 

WKUP_R5FSS0_0: ***WARNING: Please close all Memory Browser Windows before attempting to initialize DDR with GELs
WKUP_R5FSS0_0: Running from R5
WKUP_R5FSS0_0: 

DDR not initialized with R5 connect.

Go to menu Scripts --> AM62 DDR Initialization -> AM62P_DDR_Initialization_ECC_Disabled to initialize DDR.

====

WKUP_R5FSS0_0: 
WKUP_R5FSS0_0: DDR programming has already been attempted. 
WKUP_R5FSS0_0: DDR Initialization GEL script is being skipped...
WKUP_R5FSS0_0: 

Please Help me out to run this example program so that i am able to run my intended UDP program

  • Hi Jayesh,

    This looks to be initialization error. Based on the prints, I am expecting that you are trying to load the core using CCS and GEL scripts. But unfortunately, since the example runs on WKUP-R5, we would need to flash the example appimage into the OSPI memory using either UART bootloader, or USB DFU.

    Can you please confirm the method that you are using to load the cores and let me know the results after using the UART uniflash method or DFU method?

    Thanks and regards,
    Teja.

  • I am first running the following command
    make -s -C source/networking/enet/core/examples/lwip/enet_lwip_cpsw/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang
    After this 
    python3 uart_bootloader.py -p /dev/ttyUSB0 \
    --bootloader=sbl_prebuilt/am62px-sk/sbl_uart.release.hs_fs.tiimage \
    --file=/home/jayesh/ti/mcu_plus_sdk_am62px_12_00_00_27/source/networking/enet/core/examples/lwip/enet_cpsw_tcpserver/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/enet_cpsw_tcpserver.release.appimage.hs_fs

    and flash this using the UART, than after that i am opening the CCS and check the UART output on the serial console which is same as of you website 

      INFO: Bootloader_runCpu:162: CPU mcu-r5f is initialized to 800000000 Hz !!!
      INFO: Bootloader_runCpu:162: CPU a530-0 is initialized to 1250000000 Hz !!!
      INFO: Bootloader_runCpu:162: CPU a530-1 is initialized to 1250000000 Hz !!!
      INFO: Bootloader_runCpu:162: CPU a531-0 is initialized to 1250000000 Hz !!!
      INFO: Bootloader_runCpu:162: CPU a531-1 is initialized to 1250000000 Hz !!!
      INFO: Bootloader_loadSelfCpu:215: CPU wkup-r5f  is initialized to 800000000 Hz !!!

    after that when i connect WKUP-R5 as target it is showing the 

    WKUP_R5FSS0_0: ***WARNING: Please close all Memory Browser Windows before attempting to initialize DDR with GELs
    WKUP_R5FSS0_0: Running from R5
    WKUP_R5FSS0_0: 

    DDR not initialized with R5 connect.

    Go to menu Scripts --> AM62 DDR Initialization -> AM62P_DDR_Initialization_ECC_Disabled to initialize DDR.

    ====

    and after following Scripts --> AM62 DDR Initialization -> AM62P_DDR_Initialization_ECC_Disabled to initialize DDR i am getting these
    WKUP_R5FSS0_0: 
    WKUP_R5FSS0_0: DDR programming has already been attempted. 
    WKUP_R5FSS0_0: DDR Initialization GEL script is being skipped...
    WKUP_R5FSS0_0: 

    and nothing else is happening

    If i am doing anything wrong please tell me and as we are using these king of board for the very first time we don't know how exactly we need to configure, if possible can we have an online meet in which you can guide how exactly i need to do these on you convenient time, today evening at 4 Pm or monday or anytime that suits you



  • Hi Jayesh,

    We are trying to replicate this issue, and will let you know the results. Please expect a response by EOD tomorrow.

    Thanks and regards,
    Teja.

  • Hi Jayesh,

    The logs seems to be from SBL null bootloader. Can you please provide more details on how you are flashing the example?

    We have verified the example with sbl_uart_uniflash, which is different from uart bootloader which you are using currently.  Can you please check with the SBL UART Uniflash method?

    Thanks and regards,
    Teja.