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.

F28M35H52C: Power up strange phenomena

Part Number: F28M35H52C

Hi,

When I power up the Concerto, it start operating only after 1 second. I see this phenomena on scope. I also added a timer which confirmed that this is a real problem.

Can you suggest me ways to investigate the reasons for this phenomena?

Thanks, Zeev

  • Hi,

    The best way to verify the same would be to load sample codes based on RAM and Flash. Do let us know what you observe.

    Regards,
    Gautam
  • Hi Gautam,

    We noticed this phenomena after switching from RAM only version to Flash version, which copies real time code from Flash to RAM.

    In RAM version we didn't have this phenomena because the Concerto is already active.

    In Flash version the 1 second delay occures BEFORE the Flash version starts operating.

    If you have other suggestions how to investigate it, please share.

    Thanks, Zeev
  • Zeev

    On reset, you are seeing the 1 second delay before the flash application starts to run?
    The boot up code doesn't come close to taking 1 second, even in worse cases. Is it possible you may be triggering MWIR (wait in reset) mode unintentionally and then disabling it? That could potentially cause some detail. Refer to the Concerto TRM for more info.

    Best Regards
    Chris
  • Chris,

    Thanks for your answer. I checked the EMU0 and EMU1 signals on Scope. Both have '1' value. Therefore according the data sheets the Concerto did not enter WIR mode. I checked also MWIR and CWIR registers. MWIR register contains the value 3. CWIR register contains the value 0.
    Do you have other suggestions?

    Best regards,
    Zeev
  • Couple of more questions -

    1) Are you using your own custom board or any board provided by TI.
    2) Are you running standalone or with debugger connected.
    3) How are you profiling your code? How are you measuring 1s time. You mentioned, you have a timer for the same. Which timer is this?
    4) Have you scoped the XRSn pin on the device to see if there are any toggle on this pin during device boot-up?

    Regards,
    Vivek Singh
  • Hi Vivek Singh,

    Thanks for your response.

    I apologize for my late answer.

    Answer to your questions:

    1. I use my own custom board.

    2. I run stand alone and with debugger connected.

    3. I use M3 timer.

    4. I have scoped XRSn pin and there was no toggle on it

    But we found the problem: The hardware implementation caused us this delay. We fixed it and the delay reduced.

    Thanks for your assistance.

    Zeev

  • Glad to know you got it working.
  • Yes, we are glad too, but it's a pity it took so much time to solve it...