I am testing FreeRTOS on an QN9090DK6 board:
IDE: MCUXpresso IDE v11.4.1 [Build 6260] [2021-09-15]
I have verified the settings for enabling backtracing in the forum posts. I am not seeing threading enabled. I am using heart_rate_sensor_freertos example project from the SDK.
All the files have been updated and running All-Stop. I reviewed the instructions in "FreeRTOS stack backtrace is disabled". I have also went through the "MCUXpresso_IDE_FreeRTOS_Debug_Guide.
What other settings do I need to verify are correct.
GDB nonstop mode disabled (using allstop mode)
FreeRTOS stack backtrace is disabled
Thanks
Chad
what debug probe are you using? Could you share a screenshot?
Note: if using J-Link, you need to turn it on in the launch configuration settings.
And threads won't show up until you have started the scheduler.
Otherwise: does the debugger console report anything useful?
I hope this helps,
Erich
I believe there are some symbols missing (maybe due optimization or because you are using the NXP FreeRTOS port). I maintain my own port which covers all optimization levels and compiler settings, anyway.
I recommend you might have a look at yet another article of mine, more specific to this problem:
It describes a debug level setting you can use for the LinkServer configuration. The latest IDE somehow has the GUI for it removed somehow, but you can edit the .launch and change the setting manually:
Then you should get a list of symbols found:
I hope this helps,
Erich
Looking the above, what do I need to update to make the peripherals supported since this is the example being provided? I am not sure if that is why the FreeRTOSDebugConfig does not have an address like your documentation shows.
Thanks
As for the FreeRTOSDebugConfig:
Check that it is indeed linked with your application (and not optimized away)
and just in case: I maintain my version here: https://github.com/ErichStyger/McuOnEclipseLibrary/blob/master/lib/FreeRTOS/Source/include/freertos_... which has been immunized against linker and compiler optimizations.
Keep in mind that for it there are two macros required:
I hope this helps,
Erich
Looking the above, what do I need to update to make the peripherals supported since this is the example being provided?
Not sure, but I guess peripherals config tools is not implemented?
You might have to check this list:
But: It would be much better if you would open a different thread for each item.
Erich
Erich,
peripherals config tools is not implemented, in the spreadsheet line 138 is the board. QN9090DK6 is the board, Cortex-M4 I would guess falls in there. If not I can create a new thread to continue and debug this issue.
Thanks
Chad
Hi @Genovation,
I hope you are doing great.
I am not sure if I am following your case.
What are you trying to achieve? What is the example that you are running?
Could you please provide more details about the issue that you have?
Regards,
Mario
I am running the heart rate sensor freetos monitor example. I am trying to see all the threads that are running to understand how the application functions.