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.

EVM TMDX470MF066HDK: Boot without XTAL or an external clock

Other Parts Discussed in Thread: TMS470MF06607, HALCOGEN

 

Sirs,

Does the TMS470MF06607 start execution if the external clock is missing? I assume the XTAL on the OSCIN pin is broken *before power-on*. 

Or the part switches the clock source to the HFLPO and start?

 

[My test result]
The "example_freeRTOSBlinky" was generated from the HAlCoGen, built, and programmed to the TMDX470MF066HDK. Then the EVB was powered-off, OSCIN=GND, and power-on.
---> The LED doesn't blink.

 

 

  • Hi,

    We are looking into this and will get back to you ASAP.

     

    Hercules forum support

  • When OSCIN is missing, the CPU should be running from HFLPO. You need to check your code with debugger. Since the OSCIN is missing, the OSCIN fail flag will be set. The code execution may be stuck in handling this error.

    Thanks and regards,

    Zhaohong

  • Thank you for your reply

    > When OSCIN is missing, the CPU should be running from HFLPO.
    I would prefer this but my test result is not.

    > You need to check your code with debugger.
    As long as my test the CCS-debugger doesn't start. Please try:
        - Program the attached CCS5 project. Terminate the debugger. --(The LED blinks.)
        - Tie the OSCIN to GND. --(The LED blink gets slower.)
        - Press the nRST button. --(The LED stops blinking.)
        - Start the CCS-debug --(Error dialog comes.)

    Error connecting to the target:
    (Error -1170 @ 0x0)
    Unable to access the DAP. 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 0.0.0.0)

    > ... The code execution may be stuck in handling this error.
    Can I ask some more detail?
    I'm afraid that, the clock source switching doesn't occure in the nRST or power-on situation. The ARM core waits for the first clock until the OSCIN recovery.

     

    ----------------------------------------------------------------------------------------
    ----------------------------------------------------------------------------------------

    Duplication test

    2768.example_freeRTOSBlinky.zip

    Could you please duplicate my problem? Please try one of the two:

     

    [Test variation #1]

    - Program the attached [example_freeRTOSBlinky.zip].
      Please see the speed of the LED blinking.

    - Power-off.

    - Tie the OSCIN to GND.

    - Power-on.
      Please find the LED doesn't blink. (NG)
      I think this implies that the clock source doesn't switch to the HF-LPO.

    - Disconnect the OSCIN from GND.
      Please find that the LED start blinking in low-speed.
      If your comment "error handler" is some error vector, the LED doesn't blink.

     

    [Test variation #2]

    - Program the attached [example_freeRTOSBlinky.zip].

    - OSCIN=GND.

    - Press the RSTn button.
      Please find the LED doesn't blink. (NG)

    - Disconnect the OSCIN from GND.
      Two kinds of results:
      [1] LED blink in low-speed.
      [2] NO LED blink.

     

  • For the TMS470M devices, if you tie oscin to GND before power on, it can not start.

    However, if you tie oscin to GND after run to somewhere (e.g. main), it will switch to the LPO (roughly 10MHz).

    This also applies to the TMS570LS20xxxx devices.

    But this does NOT apply to the TMS570LS0x, LS1x, LS21x, LS3x devices. They can start up with oscin tied to GND.

    Does this answer your quesiton?

    Regards,

    Haixiao