- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it possible to use trace level on tag BCM 20737 for the firmware debug?
I find in dbfw_app.h, there is trace level for different model to apply.
To categorize system trace as different function or level but from header file,
it says it's workable on BCM2045 so dont know it can be workable on 20737 or not.
If yes, what else compiler option to be switched on?
Solved! Go to Solution.
- Labels:
-
Debug
-
Manufacturing and Test
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
trace() from dbfw.h is currently not available to the application. You can only use ble_trace*() functions in the app.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Leo,
When you download the SDK 2.2.1 WICED-Smart-SDK-2.2.1-IDE-Installer (Windows) , take a look at hello_sensor.c application:
extern UINT32 blecm_configFlag ;
blecm_configFlag |= BLECM_DBGUART_LOG | BLECM_DBGUART_LOG_L2CAP | BLECM_DBGUART_LOG_SMP;
Thanks
JT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi JT,
From ur suggestion, after checking, it is the BLE debug trace.
Currently we need APP level debug trace, and I find one function call as below in Dbfw_app.h,
extern void trace(UINT32 level_module_id, UINT32 fid, UINT32 line, UINT32 var);
but after I use this function, it doesn't have UART trace so dont know any problem of my configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
trace() from dbfw.h is currently not available to the application. You can only use ble_trace*() functions in the app.