• State
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 162 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM2732: C66 GPIO LED Blink Debugging Issues

Konstantinos Skyvalakis
Prodigy 130 points
Part Number: AM2732


Hi,

Whenever I am trying to debug this solo C66 example project that came with the AM2732 MCU SDK I just cant get the debugger to start and I am getting this error.

TI XDS110USB Debug Probe/C66xx_DSP Error connecting to the target: (Error -6305) PRSC module failed to write to a router register. (Emulation package 20.3.0.3656) 

The equivalent project on the R5_0 can be debugged normally. Furthermore, if I copy the contents of the C66 solo project and paste them inside the C66 of an empty system project and hit debug on the system project everything works normally again. 

But my questions remains. Why can't I just debug the solo C66 project.

Thank you in advance.

Best regards,

Konstantinos

  • 0
    TI__Guru 54308 points

    Hi Konstantinos,

    These type of error are sourced in hardware.

    Please make sure the core is initialized properly before connecting.

    Also make sure the EVM is powered up correctly and the power supply is enough to turn the EVM on.

    Please refer prsc-errors for details. 

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 130 points

    Hi Tushar,

    Obviously my EVM is powered up correctly with a 12V PSU and I have both cables (FTDI and XDSdebugger) attached

    I also said the exact same project that is only on R5_0 works properly and I am able to debug it through CCS 20.2.0.

    However, what do you mean by core initialization?

    I only import in CCS the project from C:\ti\mcu_plus_sdk_am273x_09_02_00_60\examples\drivers\gpio\gpio_led_blink\am273x-evm\c66ss0_nortos

    and i hit debug project in the imported C66 project and I get the above error.

    Do I have to do some extra initialization before I hit debug?

    Thanks.

    K.

  • 0 in reply to Konstantinos Skyvalakis
    TI__Guru 54308 points

    Make sure you have the required power supply as stated in the EVM user guide. Please refer image below.

    Please follow the steps mentioned at EVM_SOC_INIT to initialize the EVM.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 130 points

    Okay so basically the EVM_SOC_INIT steps are connect the cables, power on the EVM, build and run the project.

    Which is something I am already doing.

    My good human please try to understand what I am saying.

    I am doing all of the things you mentioned so far.

    I import in CCS the project from C:\ti\mcu_plus_sdk_am273x_09_02_00_60\examples\drivers\gpio\gpio_led_blink\am273x-evm\c66ss0_nortos

    I build it successfuly and when I hit debug I get the error shown in my first message.

    IF I IMPORT THE EXACT SAME PROJECT THAT TI HAS ALSO IMPLEMENTED ON R5 FROM: C:\ti\mcu_plus_sdk_am273x_09_02_00_60\examples\drivers\gpio\gpio_led_blink\am273x-evm\r5fss0-0_nortos

    THEN MAGICALLY EVERYTHING WORKS.

    Best regards,

    K.

  • 0 in reply to Konstantinos Skyvalakis
    TI__Guru 54308 points

    Hi,

    I had tried the same steps, initialized the EVM with SBL NULL binary. Put the EVM in QSPI boot mode. Launch and load the binary on C66 core.

    Please refer to the below steps shown in the video and check are you missing any.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 130 points

    Hi,

    In your last reply you said to do the EVM_SOC_init procedure where clearly the 3rd step in that procedure is to have the EVM in NO_BOOT MODE.

    Now you are telling me to put the EVM in QSPI boot mode. This is not mentioned AT ALL anywhere inside the MCU+ SDK User Guide: https://software-dl.ti.com/mcu-plus-sdk/esd/AM273X/latest/exports/docs/api_guide_am273x/EXAMPLES_DRIVERS_GPIO_LED_BLINK.html

    It is also not mentioned anywhere in the given example code files as a comment inside the C code.

    Why does the C66 project need QSPI boot mode to work and the R5 project works with NO_BOOT mode?

    How am I supposed to know which of your example projects need QSPI boot mode to work and which don't?

    Thanks,

    K.

  • 0 in reply to Konstantinos Skyvalakis
    TI__Guru 54308 points

    In the NO BOOT mode also we have to do the initialization of the core. When you connect to the R5F0-0 core then the GEL scripts will run and initialize the SOC. After SOC initialization, you should be able to connect with all cores.

    You might not be running the GEL scripts when configuring NO BOOT mode.

    In the QSPI mode the initialization SBL binary are already flashed and will run as soon as the EVM is powered on.

    Regards,

    Tushar