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.

Unexpected periodic reset on XRST

Other Parts Discussed in Thread: CONTROLSUITE

Dear colleagues,

I am testing an application on the Concerto F28M35xx controlCARD. The application has been compiled successfully and works well in several concerto cards. However, there is a control card that doesn't allow me to start a debug session. I receive the following error message from the debugger when I try to do it:

Cortex_M3_0: Error connecting to the target: (Error -1266 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.0.872.0) 

this error message is sometimes replaced by this other:

Cortex_M3_0: Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.

After reading some posts of this forum, I found out that the cause of that messages could be an unexpected voltage level on the XRST signal so I probed the signal with my scope.  Check the capture below. It shows the XRST voltage during the connection process (press the button start debug session).

This result mismatches those obtained with the other controlcards that works well and where the XRST voltage is constant  and approx. equal to Vdd (3.3V). Therefore, I assume that this behavior is unexpected. 

Do anyone have any theory about the reason of this unexpected behavior?

PD: I don't think it is due to an inadequate voltage level on Vdd because I checked it and  seems to be ok (Vdd = 3.25V).

Regards, Juan.

  • Hi Juan,

    This link would be helpful, check it out:

    http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/319156.aspx

    Regards,

    Gautam

  • Juan,

    that looks like this device is going into multiple resets, change the boot mode swtich on the control card to Parallel boot or Serial boot and try?

     

    Best Regards

    Santosh

  • Hi everyone, thanks for your replies.

    To Gautam: I checked the link http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/319156.aspx, It was very clarifying.

    To Santosh: I tried your proposal but it didn't work. The error message is still there.

    Update info: I have some news about the problem. I've detected that the Cortex_M3 loader error only happens when I try to load the program into the flash memory. Everything works well when I load the program into The RAM.

    The register MRESC (M3 reset cause register) show the value of 0x000009. Accorting to the TRM, It indicates that the cause of the reset is both the external signal XRST and the WDT0 (watchdog timer 0). I also checked the value at address location "0x200000 to 0x200020" and "0x27FFF0 to 0x27FFDC" as Vivek Singh suggests in the post link mentionated by Gautam . All values are 0xFFFF_FFFF.

    Regards, Juan.

  • Juan,

    are you using latest CCS version, if not please try that? When you changed the boot mode pins to Parallel boot or Serial boot, did you still see the toggles on XRSn pin?

    Best Regards

    Santosh Athuru

  • Hi Satosh,

    Santosh Athuru said:
    are you using latest CCS version

    No, I  currently use CCS v5.3.0.  Do you really think this issue is related to CCS version?

    Santosh Athuru said:
    When you changed the boot mode pins to Parallel boot or Serial boot, did you still see the toggles on XRSn pin?

    Yes, The toggle is always there regardless the boot mode. Moreover, It appears as soon as the board is powered.

    Regards, Juan.

  • Juan,

    using latest version of CCS5 is preferred. Is it is same version of Silicon on the control cards that are working and on the control card that is not working? can you tell what the markings on Silicon on the non-working control card say? what are the markings on the one that works?

    toggling of XRSn when boot mode is set to parallel or serial boot mode shouldn't happen. It would happen if OTP memory is corrupted or not programmed correctly.

     

    Best Regards

    Santosh

     

  • Hi Satosh, I finally updated CCS to its latest version 5.5. I tried to load the flash version of the project setup_m3 (v160) and the problem persisted but it disappeared when I upgraded to the version v200. Could you give some some insight about what was happening? I attach the info about the silicon version of cards as you asked me in your previous post.

    Regards, Juan

    Device 1 (it runs ok with v160 )
    =========
    Marked with X.
    Package marking code = Blank
    DIDO register = 0x20400000
    then => Rev.: 0

    Device 2  (it doesn't run under v160 if flash configuration is applied)
    =========
    Package marking code = B, then => Rev.: B

  • Juan,

    so are you saying that v160+REVB Silicon combination, the application is getting started but then the device is getting into resets?

    You should be using the latest drivers with REVB. There are a lot of fixes done to F28M35x REV0 (as mentioned in the errata). you can compare the sources (functions that are used from driverlib) between v160 and v200 (or latest) to see what's different, all the sources are available under controlSuite device support.

     

    Best Regards

    Santosh

  • Satosh, rev.b + v160 runs in RAM but not in Flash (cortex loader error and periodic reset).

    Regards