To reroute your printf calls to SWO the following settings must be set in Keil uVision: This option is only available when using ARM compiler 6 or later in Keil MDK-ARM. Support for SEGGER_RTT_ASM_ARMv7M.S is available when using "armclang" as assembler. ![]() To display the messages you can use the J-Link RTT Viewer for example which is part of the J-Link software package. Now select STDOUT and set it to Variant User:Īfter that your project should build and you can use printf via RTT in your application. First add also the corresponding syscalls file to your application.Īdditionally enable STDOUT retargeting via the "Manage Run-Time Environment" button: printf to use RTT, additional steps are necessary. You can now use the RTT API directly in your application and send data back and forth between target and host PC. Generally if you want to use RTT in Keil all you need to do is add the RTT sources to your project as explained in the J-Link user manual. MTB(partially)/ETM trace is supported for Cortex-M0, M0+, M3 and M4.Full support for SWO trace J-Link and J-Trace debug probes.Trace support before V5.30 of the Keil MDK-ARM Start the debugging session and open an "Instruction Trace" window.Set Trace Port to "Sync Trace Port with 4-bit Data".Click Settings to open the "Target Driver Setup" dialog.Set the created file as Initialization File.Open the dialog "Options for Target - Debug".ini file has to be created for the device to be traced: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |