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.

Concerto (F28M35) standalone startup problem

Scenario - Concerto based PCB with TI XDS100v2 hardware (exactly the same as the TI development PCB) 

I have two PCBs, one with a rev0 silicon Concerto and another with a revB silicon device.

I have boot code that runs fine on the rev0 silicon device.

The same boot code runs fine on the revB silicon, when the USB cable to the XDS100v2 is connected.

However when the USB cable is unplugged the C28 core does not run. And the M3 stalls in

IPCMtoCBootControlSystem(CBROM_MTOC_BOOTMODE_BOOT_FROM_FLASH);

 

  • Hi Andy,

    Could you take a look at the below post and see if it helps? I think it will be relevant to your situation.
    http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/317040/1113444.aspx#1113444


    Thank you,
    Brett

  • Hi Brett -

    I have simplified things - just built and loaded "F28M35x_examples_Master\blinky" - with no code in the c28.

    Run blinky under emulator control and LED flashes at 5Hz.

    Power down the target, shut down code composer & unplug the emulator USB cable.

    Power up the target - LED flashes at ~2.5Hz.

    Power down target, plug emulator USB back in to PC & power up target - LED flashes at 5Hz.

    Power down target, unplug emulator USB, and connect it to a standalone usb port (+5v only), power up, LED flashes at ~2.5Hz.

    I think that the clocking of the revB silicon is running slow when the emulator is not powered and enumerated by the PC.

    I then disconnected TRST, EMU0 & EMU1 (leaving the pull up/down resistor) - Blinky still runs slow when the USB is not plugged into the PC.

    I will try disconnecting the other JTAG signals on monday.

    Andy

     

     

  • Problem found - A dry solder joint on the reset generator - This resulted in a very short reset, releasing the concerto before the XTAL & PLL in the main clock had started. This caused the missing clock interrupt to occur and "limp mode" to be entered.

    When the emulator USB cable was attached, enough power was provided by the JTAG signals to start the XTAL bfore the main power was applied.