memo_iwrl6432_ccs_dbg_problem.docx

具体内容在文件里面

Hello, 

Thank you for including all of the pictures in your post to show the steps that you are taking. If you have a specific question, please post the question in English for this forum. 

Best Regards,

Josh

from the line "System_init();" press F6 to the line "vTaskStartScheduler();"
at the line "vTaskStartScheduler();" press F6, the console will print:
"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.13.0.00201)
"

Please refer to<memo_iwrl6432_ccs_dbg_cannot_run_target_CPU_en.docx>

memo_iwrl6432_ccs_dbg_cannot_run_target_CPU_en_2023_1228.docx

Hello, 

Thank you for the clarification. I see that you are rebuilding the hello world example in CCS and then loading that rebuilt .out file. Have you made any changes to the hello world project before rebuilding? Also, the mmWave L SDK provides prebuilt binaries for all examples including the .out files. Can you try loading the prebuilt .out files from the SDK instead and see if the issue persists? These files are present at <MMWAVE_SDK5_INSTALL_DIR>\examples\hello_world\xwrL64xx-evm\m4fss0-0_freertos\ti-arm-clang. 

Best Regards,

Josh

1: I didn't change the source code of the "hello world" project

2: debug prebuilt binaries of  hello_world.release.out, can not load main.c, please refer to

<memo_iwrl6432_ccs_dbg_cannot_load_mainc_by_prebuilt_2023_1229_01.docx>memo_iwrl6432_ccs_dbg_cannot_load_mainc_by_prebuilt_2023_1229_01.docx

1: pressing the reset button, S2 (RESET_SW),

2: launch configuration “IWRL6432.ccxml”

3:show cores

4:connect

5:connect

6:load program 

7:E:\gitee\soft_study\sensor_ti\iwrl6432\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang\Debug\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang.out

8: in main.c step to "vTaskStartScheduler();"

9: 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.13.0.00201)

I try this steps again and again(> 100 times ) ,depressed helpless 

I encountered the same problem, I'm on another computer.
Is there any problem with this IWRL6432BOOST board, or is the SOP switch wrong?

problem: Step into, Step over, is disable(grey) after load program
1: pressing the reset button, S2 (RESET_SW),
2: launch configuration “IWRL6432.ccxml”
3:show cores
4:connect target <Texas Instruments XDS110 USB Debug Probe/CS DAP_O>
5:connect target <Texas Instruments XDS110 USB Debug Probe/Cortex M4 0 >
6:0x0040C6CC (no symbols are defined)
7:load program E:\gitee\soft_study\sensor_ti\iwrl6432\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang\Debug\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang.out
8: Step into, Step over, is disable(grey),
9:Reload program E:\gitee\soft_study\sensor_ti\iwrl6432\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang\Debug\hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang.out
10: in main.c step to "vTaskStartScheduler();"
11: on the line "vTaskStartScheduler();", <Step over> will print in console <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.13.0.00201)>
I try this steps again and again(> 100 times )

Hello, 

Can you please take a picture of the EVM and share it here so that I may see the switch configuration?

Best Regards,

Josh

rojects that use FreeRTOS cannot be debugged, (how to solve this problem);
but the project motion_and_presence_detection that use freertos can be debugged.

import ccs project from C:\ti\MMWAVE_L_SDK_05_03_00_02\examples
1: Enable the tool icons of Stepinto, Stepover,StepReturn
int main()
{ "start at this line"
after "load program"
there are projects:
dpl_demo_xwrL64xx-evm_m4fss0-0_nortos_ti-arm-clang
empty_xwrL64xx-evm_m4fss0-0_nortos_ti-arm-clang
hello_world_cpp_xwrL64xx-evm_m4fss0-0_nortos_ti-arm-clang
motion_and_presence_detection_demo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
uart_echo_xwrL64xx-evm_m4fss0-0_nortos_ti-arm-clang

2: Disable the tool icons of Stepinto, Stepover,StepReturn
and can not entry int main()
after "load program"
there are projects:
dpl_demo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
empty_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
hello_world_cpp_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
posix_demo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
task_switch_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
uart_echo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang

3: There are the following phenomena:
3.1: only motion_and_presence_detection that use freertos can be debugged,
3.2: Other projects that use FreeRTOS cannot be debugged, (how to solve this problem)
3.3: Projects that don't need freertos can be debugged

import hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
from MMWAVE_L_SDK_05_01_00_03-Windows-x86-Install.exe can debug
but from MMWAVE_L_SDK_05_03_00_02-Windows-x86-Install.exe cannot debug
please repeat it and solve this problem and Hopefully subsequent releases don't have this issue.

Hello, 

Thank you for sharing a picture of your setup. Please allow me a day to attempt to replicate the issue with the steps you have provided. I will reply here by the end of the day tomorrow with my findings.

Best Regards,

Josh

Do you reproduce the issue and how do I fix it?

Hello, 

Sorry about the delay here. We are still looking into this issue. I do not have a solution for you right now. Please let me continue to look into this. I will give an update here within the next 24 hours. 

Best Regards,

Josh

Hi, 

Just to give you an update, I am still looking into this but need more time. You can expect a reply from me here early next week. Thank you for your patience.

Best Regards,

Josh

Hello, 

I apologize for the delayed response. Are you still facing issues here? 

?? ? said:

import hello_world_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang
from MMWAVE_L_SDK_05_01_00_03-Windows-x86-Install.exe can debug
but from MMWAVE_L_SDK_05_03_00_02-Windows-x86-Install.exe cannot debug

I am not able to replicate the issues that you are seeing here. This project can be debugged successfully on my end with the following setup/procedure. 

Setup:

CCS Version 12.5. 

MMWAVE_L_SDK_05_03_00_02

S1 settings: 1.1 ON, 1.2 OFF, 1.3 OFF, 1.4 OFF, 1.5 ON, 1.6 OFF. 

S4 settings: 4.1 OFF, 4.2 OFF, 4.3 OFF, 4.4 ON

S5 settings: 5.1 OFF, 5.2 OFF

Procedure:

1. Connect device to PC via USB after confirming switch settings mentioned above. 

2. In CCS, import hello world freertos project from SDK located at C:\ti\MMWAVE_L_SDK_05_03_00_02\examples\hello_world\xwrL64xx-evm\m4fss0-0_freertos\ti-arm-clang

3. In CCS Project Explorer Window, Right-click on hello world project and select Build Project. 

4. After project builds, right-click on target configuration and select Launch Selected Configuration

5. In CCS Debug window, right-click on XDS110 USB Debug Probe_0/Cortex_M4_0 and select Connect Target.

6. Click CPU Reset icon in the CCS toolbar. 

7. In the CCS toolbar select the load program Icon. 

8. In the window that opens, select Browse project...

9. In the window that opens, expand the hello world freertos project, then the subfolder named Debug and select the hello world .out file. Select OK.

10. Program is paused at entry point. 

11. If breakpoints are placed, execution successfully pauses at breakpoint. 

12. When execution is resumed, Hello World! is successfully printed to the console.

Please confirm that you are following all of the above steps exactly. 

Best Regards,

Josh

this problem have not resolved

Hello,

Please confirm, have you followed the instructions I posted above? Do you still see "Cortex_M4_0: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI." ?

Best Regards,

Josh