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.

IWRL6432BOOST: Error on Resume during CCS Debug

Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

Hi Radar champs

If customers follow the attached document and run debug mode, an error occurs during Resume and asks for a solution.

8546.xWRL6432_APL_CCS_debug_guide.pdf

CS_DAP_0: GEL Output: Starting FEC Memory Init
CS_DAP_0: GEL Output: FEC RAM Memory Init Completed
CS_DAP_0: GEL Output: FEC Shared RAM Memory Init Completed
CS_DAP_0: GEL Output: FEC Patch / Data RAM configuration Done
CS_DAP_0: GEL Output: APP RAM1
CS_DAP_0: GEL Output: APP RAM2
CS_DAP_0: GEL Output: APP RAM3
CS_DAP_0: GEL Output: APPSS RAM configuration
CS_DAP_0: GEL Output: HWASS SHRD RAM0
CS_DAP_0: GEL Output: HWASS SHRD RAM1
CS_DAP_0: GEL Output: HWASS SHRD RAM0 configuration
CS_DAP_0: GEL Output: device_wakeup in application mode done 
CS_DAP_0: GEL Output: M4 reset releasedCortex_M4_0: 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.10.0.00080) 
Cortex_M4_0: 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.10.0.00080) 
Cortex_M4_0: 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.10.0.00080) 

  • Hi, 

    Looking into this. Expect a response later today or tomorrow. 

    Best Regards,

    Josh

  • Hello,

    This error seems to indicate that the device is not set in the correct mode. The debugging procedure described in the guide you linked requires the device to be set in Debug mode. Please advise the customer to set the device in debug mode (S1.1=ON, S1.2=ON) and repeat the debugging procedure. 

    Best Regards,

    Josh

  • Hello Josh.

    I have completed the setup about debug mode(S1.1=ON, S1.2=ON)

    When i retry debug mode

    I can see some error message

    This is the message that appears when 'Load Memory'

    could you check it?

    CS_DAP_0: GEL Output: Starting FEC Memory Init
    CS_DAP_0: GEL Output: FEC RAM Memory Init Completed
    CS_DAP_0: GEL Output: FEC Shared RAM Memory Init Completed
    CS_DAP_0: GEL Output: FEC Patch / Data RAM configuration Done
    CS_DAP_0: GEL Output: APP RAM1
    CS_DAP_0: GEL Output: APP RAM2
    CS_DAP_0: GEL Output: APP RAM3
    CS_DAP_0: GEL Output: APPSS RAM configuration
    CS_DAP_0: GEL Output: HWASS SHRD RAM0
    CS_DAP_0: GEL Output: HWASS SHRD RAM1
    CS_DAP_0: GEL Output: HWASS SHRD RAM0 configuration
    CS_DAP_0: GEL Output: device_wakeup in application mode done
    CS_DAP_0: GEL Output: M4 reset releasedCortex_M4_0: 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.10.0.00080)

    Thanks

  • Hi,

    After changing the switch settings have you power cycled the device? E.g. disconnect the USB connecting the device to the PC then reconnect. This step is necessary to ensure that the new SOP configuration takes effect.

    Best Regards,

    Josh

  • Hi Josh

    Thanks for your reply.

    I've tried several times to reapply power

    But there is the same error.

    CS_DAP_0: GEL Output: Starting FEC Memory Init
    CS_DAP_0: GEL Output: FEC RAM Memory Init Completed
    CS_DAP_0: GEL Output: FEC Shared RAM Memory Init Completed
    CS_DAP_0: GEL Output: FEC Patch / Data RAM configuration Done
    CS_DAP_0: GEL Output: APP RAM1
    CS_DAP_0: GEL Output: APP RAM2
    CS_DAP_0: GEL Output: APP RAM3
    CS_DAP_0: GEL Output: APPSS RAM configuration
    CS_DAP_0: GEL Output: HWASS SHRD RAM0
    CS_DAP_0: GEL Output: HWASS SHRD RAM1
    CS_DAP_0: GEL Output: HWASS SHRD RAM0 configuration
    CS_DAP_0: GEL Output: device_wakeup in application mode done
    CS_DAP_0: GEL Output: M4 reset releasedCortex_M4_0: 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.10.0.00080)

    I will explain my testing process

    I've tried example about the 'hello world'

    1. I used the 'visiualizer' to download file which is the 'hello_world.debug.appimage'

    2. After download, I changed switch for debug mode

    3. I lunched the CCS and selected the Lanuch Selected Configuration

        *This is on page 3 of the '8132.xWRL6432_APL_CCS_debug_guide.pdf' 

    4. Here's one difference between the documentation(8132.xWRL6432_APL_CCS_debug_guide.pdf) and my screen

        You can see it in the image below.

        In the fig1, you can see two core Corent_M4_0 and Cortex_M3_0

        But in the fig2, you can't find Cortex_M3_0 

        is it right?

         

    [fig1. documentation]

    [fig2. my screen]

    5. After that I've try the on pages 4~6 of the '8132.xWRL6432_APL_CCS_debug_guide.pdf' 

       I can read on console “M4 reset released”

    6. The on pages 7 of the '8132.xWRL6432_APL_CCS_debug_guide.pdf',

        After that, I can set the image below the fig3

        I think that this is so strange

        Could you check it?

    [fig3 After connect to Cortex M4]

    Thanks

    Regards

  • Hello, 

    Thank you for giving a detailed account of the steps you've taken. This is very helpful for me to assist you in resolving the issue. Couple of notes:

    • There is no need to flash the 'hello_world.debug.appimage' to the device before beginning the debug procedure. The program will be loaded to the device in CCS using 'hello_world.debug.out' file. However, I do not believe this is what is causing the problem you are seeing. 
    • I apologize about the confusion regarding the images in the pdf guide. The images were likely taken from a previous version in which the target configuration file used showed both the M3 and M4 cores. The current target configuration does only show the M4 core so you have nothing to worry about there. Thank you for pointing this out, we will update the images in the guide for improved clarity. 
      • The on pages 7 of the '8132.xWRL6432_APL_CCS_debug_guide.pdf',

            After that, I can set the image below the fig3

            I think that this is so strange

            Could you check it?

      This is also expected after connecting to the M4. No issue here. 

    It seems that I have been able to replicate the error that you are seeing. All of the steps you have listed so far are correct besides the first step which is unnecessary. I believe the error may be occurring based on what you do next after this point. Once you have connected to the M4 (fig. 3) you must reset the CPU, this can be done with the keyboard shortcut Ctrl+Shift+R or by clicking on the circled icon in the image below. 

    After resetting the CPU you can follow the remaining steps in the pdf guide. Starting with loading the .out file. The pdf guide references the Out-of-Box demo (Presence and Motion Detect) but the same steps can be used for debugging the hello world example. 

    I hope this helps! Please let me know if this does not resolve your issue.

    Best Regards,

    Josh

  • Hello Josh.

    Thanks for your reply

    I have solved the problem with your help
    I was missing the CPU reset as you said
    Thank you very much
    Have a nice day!

  • Hi,

    I'm glad you were able to resolve your issue. Please don't hesitate to create an additional thread if you have any further questions.

    Best Regards,

    Josh