• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 138 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDSCNCD263: Stuck at GEL Expression: On target connect()

Ajit Ladgaonkar
Intellectual 566 points

Part Number: TMDSCNCD263
Other Parts Discussed in Thread: AM2634,

Hi Team,

 

Whenever, we aretrying to load the code into AM2634 on TMDSCNCD263. We are getting below error and its stuck there itself. Requesting for your support on this. We need to resolve this asap to meet project milestones.

image.png

Console output for reference:

Cortex_R5_0: GEL Output: Loading Gel Files on R5F0 
Cortex_R5_0: GEL Output: Gel files loading on R5F0 Complete
Cortex_R5_0: GEL Output: ***OnTargetConnect() Launched***

Cortex_R5_0: GEL Output: AM263x Initialization Scripts Launched. 
Please Wait...


Cortex_R5_0: GEL Output: AM263x_Cryst_Clock_Loss_Status() Launched
Cortex_R5_0: GEL Output: Crystal Clock present 
Cortex_R5_0: GEL Output: AM263x_SOP_Mode() Launched
Cortex_R5_0: GEL Output: SOP MODE = 0x00001000    
Cortex_R5_0: GEL Output: 
 ERR... Reserved boot mode
Cortex_R5_0: GEL Output: AM263x_Read_Device_Type() Launched
Cortex_R5_0: GEL Output: EFuse Device Type Value = 0x000000AA    
Cortex_R5_0: GEL Output: AM263x_Check_supported_mode() Launched
Cortex_R5_0: GEL Output: 
 The Device supports both LockStep & Dual Core mode 
Cortex_R5_0: GEL Output: 
 mode = 1 
Cortex_R5_0: GEL Output: MSS_CTRL Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_TOP_RCM Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_RCM Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_IOMUX Control Registers Unlocked
Cortex_R5_0: GEL Output: TOP_CTRL Control Registers Unlocked
Cortex_R5_0: GEL Output: 

*** R5FSS0 Reset DualCore ***
Cortex_R5_0: GEL Output: 

***R5FSS1 Reset DualCore ***
Cortex_R5_0: GEL Output: R5F ROM Eclipse
Cortex_R5_0: GEL Output: R5FSS0_0 Released
Cortex_R5_0: GEL Output: R5FSS0_1 Released
Cortex_R5_0: GEL Output: R5FSS1_0 Released
Cortex_R5_0: GEL Output: R5FSS1_1 Released
Cortex_R5_0: GEL Output: 

 All R5F Cores Released for program load
Cortex_R5_0: GEL Output: L2 Mem Init Complete
Cortex_R5_0: GEL Output: MailBox Mem Init Complete
Cortex_R5_0: GEL Output: ******** R5FSS0/1 Dual Core mode Configured*****

 

Thanks,

Ajit

  • 0
    TI__Mastermind 27132 points

    Hi Ajit,

    1. Can you share the CCS version you are using? And what revision of AM263x-CC you have?

    2. Can you share the bootmode you wish to use?

    Looks like the gel script is getting stuck in the PLL or peripheral initialization.

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Intellectual 566 points

    Hi Shaunak,

    CCS version: 12.7.0.00007 

    AM263x-CC : Rev A (Part No. tmdscncd263)

    QSPI - 4S Fallback UART boot mode

    Please let me know. Because this error, I can not use one EVM board.

    Thanks,

    Ajit

  • 0 in reply to Ajit Ladgaonkar
    TI__Mastermind 27132 points

    Hi Ajit,

    If you intend to use QSPI and UART boot-modes, you can ignore the above errors and remove the gel script from your .ccxml files in CCS.

    Since your boot-loader will already do the initializations, you dont really need the gel script to initialize memory and peripherals again.

    Usually the gel scripts are used with DEV Bootmode.

    in your .ccxml target config file, you can clear out the highlighted path, save the file and relaunch the target config.

    The gel script should not run now and get stuck in errors.

    Looks like there might be some version mis-match between the hardware revision and the software version of gel script being used, causing the gel script to get stuck, but for this case since we are not using DEV Bootmode, this can be completely removed. The SBL will take care of the configs in QSPI bootmode

    Regards,
    Shaunak