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.

TDA3MV: TDA3 CCS10 Debug issue(SYSBOOT7=0)

Part Number: TDA3MV

Hi team,

Using CCS Debug, The reported problems are: Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, Confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (E.g. lower TCLK). (Emulation package 9.4.0.00129), Reset was tested, only hardware power-on reset was used on the customer's board, soft reset pin was pulled high. Another attempt was to downfrequency the TCK of JTAG to 1MHz, but the same problem was reported. The customer suspects the configuration switch SYSBOOT15-0. The log is as follows: there are a lot of timeouts:

Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Cortex M4 Startup Sequence DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Cortex M4 Startup Sequence In Progress... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Cortex M4 Startup Sequence DONE! <<<---
ARP32_EVE_1: GEL Output: --->>> Configuring EVE Memory Map <<<---
ARP32_EVE_1: GEL Output: --->>> EVE Memory Map Done! <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence Begins ... <<<---
Cortex_M4_IPU1_C0: GEL Output: Core Reset has occurred.

Cortex_M4_IPU1_C0: GEL Output: --->>> A device reset occurred <<<---
Cortex_M4_IPU1_C0: GEL Output: ==================================================
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG3.0 device detected =========
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
Cortex_M4_IPU1_C0: GEL Output: ==================================================
Cortex_M4_IPU1_C0: GEL Output: Core Reset has occurred.

Cortex_M4_IPU1_C0: GEL Output: ==================================================
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG3.0 device detected =========
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
Cortex_M4_IPU1_C0: GEL Output: ==================================================
Cortex_M4_IPU1_C0: GEL Output: --->>> All Control module lock registers are UNLOCKED <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> Changing RTI1 reaction type to avoid RTI1 resetting the device after 3 minutes... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> Starting IPU A-MMU configurations... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> IPU A-MMU configuration completed. <<<---
Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR and DPLL configuration Based on Package selection pin status(Sysboot[7]) <<<---
Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
Cortex_M4_IPU1_C0: GEL Output: --->>> 15x15 Package Detected(SYSBOOT[7]=0)... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPPNOM in progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 clock config in progress...
Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP_DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000C8
Cortex_M4_IPU1_C0: GEL Output: TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000D0
Cortex_M4_IPU1_C0: GEL Output: TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000D8
Cortex_M4_IPU1_C0: GEL Output: TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x00000130
Cortex_M4_IPU1_C0: GEL Output: TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 initialization starts (TI 15x15 EVM)... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 Initialization is in progress ... <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in progress...
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in DONE!
Cortex_M4_IPU1_C0: GEL Output: Launch full leveling
Cortex_M4_IPU1_C0: GEL Output: Updating slave ratios in PHY_STATUSx registers
Cortex_M4_IPU1_C0: GEL Output: as per HW leveling output
Cortex_M4_IPU1_C0: GEL Output: HW leveling is now disabled. Using slave ratios from
Cortex_M4_IPU1_C0: GEL Output: PHY_STATUSx registers
Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 532MHz Initialization is DONE! <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for Vision Platform <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for RGMII usage on EVM Platform <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW MDIO Pad Configuration <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW MDIO Pad Configuration <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW RGMII0 Pad Configuration <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW RGMII0 Pad Configuration <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for RGMII usage on EVM Platform <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for Vision Platform <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence DONE !!!!! <<<---
Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cortex_M4_IPU1_C0: GEL Output: For STM based tracing on TI EVMs,
Cortex_M4_IPU1_C0: GEL Output: run 'TDA3x EVM I2C EXPANDER CONTROL -> Enable_Trace_Pins()' function from Scripts menu on M4/CS_DAP_DebugSS
Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cortex_M4_IPU1_C0: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Target Connect Sequence Begins ... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> A device reset occurred <<<---
Cortex_M4_IPU1_C1: GEL Output: ==================================================
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx PG3.0 device detected =========
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx GP Device detected ===========
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx 15x15 Device detected ===========
Cortex_M4_IPU1_C1: GEL Output: ==================================================
Cortex_M4_IPU1_C1: GEL Output: Core Reset has occurred.

Cortex_M4_IPU1_C1: GEL Output: ==================================================
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx PG3.0 device detected =========
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx GP Device detected ===========
Cortex_M4_IPU1_C1: GEL Output: ========= TDA3xx 15x15 Device detected ===========
Cortex_M4_IPU1_C1: GEL Output: ==================================================
Cortex_M4_IPU1_C1: GEL Output: --->>> All Control module lock registers are UNLOCKED <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> Changing RTI1 reaction type to avoid RTI1 resetting the device after 3 minutes... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> Starting IPU A-MMU configurations... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> IPU A-MMU configuration completed. <<<---
Cortex_M4_IPU1_C1: GEL Output: ------------------------------------------------------------------------------------------
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR and DPLL configuration Based on Package selection pin status(Sysboot[7]) <<<---
Cortex_M4_IPU1_C1: GEL Output: ------------------------------------------------------------------------------------------
Cortex_M4_IPU1_C1: GEL Output: --->>> 15x15 Package Detected(SYSBOOT[7]=0)... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> PRCM Clock Configuration for OPPNOM in progress... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> CORE DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C1: GEL Output: --->>> CORE DPLL OPP already locked, now unlocking....
Cortex_M4_IPU1_C1: GEL Output: --->>> CORE DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C1: GEL Output: --->>> PER DPLL OPP 0 clock config in progress...
Cortex_M4_IPU1_C1: GEL Output: --->>> PER DPLL already locked, now unlocking
Cortex_M4_IPU1_C1: GEL Output: --->>> PER DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C1: GEL Output: --->>> DSP_GMAC DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C1: GEL Output: --->>> DSP_GMAC DPLL already locked, now unlocking....
Cortex_M4_IPU1_C1: GEL Output: --->>> DSP_GMAC DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C1: GEL Output: --->>> EVE_VID_DSP DPLL OPP 0 clock config is in progress...
Cortex_M4_IPU1_C1: GEL Output: --->>> DSP DPLL already locked, now unlocking....
Cortex_M4_IPU1_C1: GEL Output: --->>> EVE_VID_DSP_DPLL OPP 0 is DONE!
Cortex_M4_IPU1_C1: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
Cortex_M4_IPU1_C1: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C1: GEL Output: module_offset: 0x000000C8
Cortex_M4_IPU1_C1: GEL Output: TIMEOUT
Cortex_M4_IPU1_C1: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C1: GEL Output: module_offset: 0x000000D0
Cortex_M4_IPU1_C1: GEL Output: TIMEOUT
Cortex_M4_IPU1_C1: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C1: GEL Output: module_offset: 0x000000D8
Cortex_M4_IPU1_C1: GEL Output: TIMEOUT
Cortex_M4_IPU1_C1: GEL Output: module_base: 0x4A009700
Cortex_M4_IPU1_C1: GEL Output: module_offset: 0x00000130
Cortex_M4_IPU1_C1: GEL Output: TIMEOUT
Cortex_M4_IPU1_C1: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR3 initialization starts (TI 15x15 EVM)... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR3 Initialization is in progress ... <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR DPLL clock config for 532MHz is in progress...
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR DPLL already locked, now unlocking....
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR DPLL clock config for 532MHz is in DONE!
Cortex_M4_IPU1_C1: GEL Output: Launch full leveling
Cortex_M4_IPU1_C1: GEL Output: Updating slave ratios in PHY_STATUSx registers
Cortex_M4_IPU1_C1: GEL Output: as per HW leveling output
Cortex_M4_IPU1_C1: GEL Output: HW leveling is now disabled. Using slave ratios from
Cortex_M4_IPU1_C1: GEL Output: PHY_STATUSx registers
Cortex_M4_IPU1_C1: GEL Output: --->>> DDR3 532MHz Initialization is DONE! <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Begin All Pad Configuration for Vision Platform <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Begin All Pad Configuration for RGMII usage on EVM Platform <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Begin GMAC_SW MDIO Pad Configuration <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx End GMAC_SW MDIO Pad Configuration <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Begin GMAC_SW RGMII0 Pad Configuration <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx End GMAC_SW RGMII0 Pad Configuration <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx End All Pad Configuration for RGMII usage on EVM Platform <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx End All Pad Configuration for Vision Platform <<<---
Cortex_M4_IPU1_C1: GEL Output: --->>> TDA3xx Target Connect Sequence DONE !!!!! <<<---
Cortex_M4_IPU1_C1: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cortex_M4_IPU1_C1: GEL Output: For STM based tracing on TI EVMs,
Cortex_M4_IPU1_C1: GEL Output: run 'TDA3x EVM I2C EXPANDER CONTROL -> Enable_Trace_Pins()' function from Scripts menu on M4/CS_DAP_DebugSS
Cortex_M4_IPU1_C1: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cortex_M4_IPU1_C1: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)

As shown in the following figure, the current 16 switch pins SYSBOOT15-SYSBOOT0 are configured from high to low as 00111000 10000001. The other SW8001 is not drawn on the hardware (it does not affect in Debug mode). In this configuration, SYSBOOT7 should theoretically be 1, but in the log is "Cortex_M4_IPU1_C1: GEL Output: --" ->>> 15x15 Package Detected (SYSBOOT[7] = 0)... <<--". Is it the effect of SYSBOOT that results in an error? (In this design, SYSBOOT7 is not connected to the switch, but directly connected to QSPI FLASH)

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi,

    May I know is there any updates?

    Thanks and Best Regards,

    Cherry

  • Cherry,

    Is this issue seen on the TI EVM or the customer board?

    Why is CCS10 important here - does it work with an older version of CCS?

    Can you please explain more about this - SYSBOOT7 is not connected to switch but directly connected to QSPI FLASH? What does this mean?

    Regards

    Karthik

  • Hi Karthik,

    Thanks for your support!

    Is this issue seen on the TI EVM or the customer board?

    They are using their own design board for debugging, which is basically the same hardware architecture as TI's development board, just removed the GPMC (CPLD+NORFLASH).

    Why is CCS10 important here - does it work with an older version of CCS?

    The CCS6.2 CCS9 CCS10 and the latest CCS11 all have been tried and the issue is the same.

    Can you please explain more about this - SYSBOOT7 is not connected to switch but directly connected to QSPI FLASH? What does this mean?

    The SYSBOOT7 pin is missing from the hardware, and the R7 pin of TDA3 has been fixed by flying wire without being pulled externally.

    But there are still some problems:

    Using XDS110 and Blackhawk 560 V2 to connect JTAG  test connection can work normally and can san the 5 cores of TDA3. But while using the example library of CCS to print "hello world", the following error is reported:

    "Cortex_M4_IPU1_C1: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)"

    Using the SDK of the development board, but still report the error like this: "a data verification error occurred, file load failed."

    Also reviewed on hardware, the power-up timing is currently 1.8 V 1.35 V 1.06 VCORE 1.06 VDSPEVE 3.3 V and then 20 M clock is enabled and POR is pulled high.

    The above waveforms are all measured using oscilloscope points, they should be ok.

    Best Regards,

    Cherry

  • Hi,

    May I know is there any updates about the info above?

    Thanks and Best Regards,

    Cherry

  • Hi Cherry,

    Using XDS110 and Blackhawk 560 V2 to connect JTAG  test connection can work normally and can san the 5 cores of TDA3. But while using the example library of CCS to print "hello world", the following error is reported:

    "Cortex_M4_IPU1_C1: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.4.0.00006)"

    Using the SDK of the development board, but still report the error like this: "a data verification error occurred, file load failed."

    Typically, you can not just build and run some example from CCS. The memory map might not match what is available on the board.

    A data verification error indicates the program you try to load is placed to invalid memory region.

    It is typically a problem with the linker command file of your example.

    Regards,
    Stanley