Smart Bluetooth Forum Discussions
As the topic, I am using wiced.1.1.0. When I called those C string function, such as strncpy, srtncmp, etc, the compiler told me they are not defined, I included string.h.
Thanks!
Show LessI'm trying to follow the steps from pages 13-14 of the quick start guide.
I don't have access to hyperterm (which has been extinct since windows vista), I've tried tera term (as suggested in the guide), and also MTTY (windows) and screen (on OSX).
In all cases the trace statements print junk like this:
HX dcXÊBH Xä „
BÑBѨ B £RH c Bˇ "ÑP o;Ä_ZrÙ ZB à¬∆
JV»Hæ⁄HJ¶HJ⁄Hä⁄HJ⁄HJ⁄HJ⁄HJ⁄Hº⁄HJ¢H∫JHJJHJ¢HJZHJJHJJHJZ∏J∫HºJHJJHJJHJHJZ⁄P 5zX roZ ¬Û÷ ˇHJZ»“ :RV ˇHJ∏J™HΩZHJöHΩJHJJRX⁄PZÛP JHrıH∫JHJ™H∫Z⁄P
I've checked bleapp_trace_enable, SW4 switches, etc. - Does anyone have an idea what could be wrong?
Are there any plans to support the SWD interface and proper debugging in a future version of the SDK & IDE?
Regards
Tim Redfern
Show Less
I tried to add some trace messages to some functions in bleapp (bletime_TimeReq()), however when I exectute the traget ( proximity_plus.c) it doesn't seem to re-compile the bleapp code. I even tried a clean build and it doesn't rebuild them. Is there a binary thats always used for all applications and are we not allowed to make modifications to the bleapp code ? Or is there a separate target to rebuild the lower bleapp libs ?
Thanks
Kartik
Show LessI have been trying to configure and run the SPI_MASTER example, after several iterations I have been able to get it to run, but one problem that I am still having is that the Chip select signal I want to output (different board that I have done a layout on for a custom application), on Port 32 and Port 33, which happen to share the PUART configuration. I tried to disable the PUART by sending in the following structure:
BLE_PROFILE_PUART_CFG puart_cfg =
{
/*.baudrate =*/ 115200,
/*.txpin =*/ PUARTDISABLE | GPIO_PIN_UART_TX,
/*.rxpin =*/ PUARTDISABLE | GPIO_PIN_UART_RX,
}
This is what was shown in the example with SPI_MASTER. Where GPIO_PIN_UART_TX = 32, and GPIO_PIN_UART_RX = 33.
The problem is that I get no output from my Chip select setting that is on Port 32. If I change the Port config to another port (port 4 for example), then the signal output works as expected. I also changed the puart_cfg to use GPIO_PIN_UART_TX = 0, and GPIO_PIN_UART_RX = 2, But still no output on port 32. So it seems like the PUART is somehow being configured on these pins no matter what I do and is not allowing me to use GPIO on these pins. Please Help!
Show LessWhen I attempt to call "bleappevt_serialize" in my code I need to include "bleappevent.h" ...
When I do include the header I get this failure. It seems it doesnt like the "bt_types.h" file referenced in the "bleappevent.h" file.
When I remove the #include "bt_types.h" statement it builds OK. Please ADVISE if this is something that needs to change or has already changed on the Broadcom side of things ... thanks
11:04:44 **** Build of configuration blood_pressure_monitor-BCM920732TAG_Q32 for project WICED-Smart-SDK ****
"C:\\Users\\vsesto\\Broadcom\\WICED\\WICED-Smart-SDK-1.1.0\\WICED-Smart-SDK\\make.exe" RAM.glucose_meter-BCM920732TAG_Q32 download
Compiling glucose_meter.c
In file included from ../../Apps/RAM/glucose_meter/glucose_meter.c:52:0:
../bleapp/utils/bleappevent.h:25:22: fatal error: bt_types.h: No such file or directory
compilation terminated.
makefile:270: recipe for target '../../build/glucose_meter-BCM920732TAG_Q32-rom-ram-Wiced-release/glucose_meter.o' failed
Makefile:286: recipe for target 'RAM.glucose_meter-BCM920732TAG_Q32' failed
make.exe[1]: *** [../../build/glucose_meter-BCM920732TAG_Q32-rom-ram-Wiced-release/glucose_meter.o] Error 1
make: *** [RAM.glucose_meter-BCM920732TAG_Q32] Error 2
11:04:45 Build Finished (took 1s.434ms)
Show LessI am just learning the Broadcom BLE stack and saw the one pager for the BCM92073X_LE_KIT.
Can someone please share a link on ordering one of these ?
Thank you for your help
Bob
Show LessI solid a BCM20732S module on a motherboard, which is designed by myself.
At first time, I can download firmware into 20732S and it can run RAM application.
After several time, the downloading operation was paralysed, eclipse console always show "Detecting device...".
Then, I want to recover 20732S. I can drive SDA pin to low when reset, but the phenomenon is the same, eclipse console show "Recovering platform ..."
What's wrong with 20732s?
BTW, I2C bus connect a temperature sensor, AD7414.
Show LessSometimes when I build the glucose profile code I see this trace statement
GPIO_WP:OFF=0
But then I dont see any other trace statements ...
It seems like the code isnt running properly for some reason.
What is the max RAM the app can be? I need to add some command parsing code to the application
Show LessThe BCM920732 HW Application Note (MMP920732HW-AN101.pdf) describes the BCM20732 Hardware Interfaces and provides sample code on how to program the various BCM20732 interfaces.
The document (dated Jan 15th, 2014) describing the Peripheral UART states your application needs to #include the "puart.h" file. Several lines later there is a call to: P_UART_INT_CLEAR(P_UART_ISR_RX_AFF_MASK).
As of SDK 1.1.0, the example code throws a fairly cryptic compiler error of: "error: lvalue required as left operand of assignment". There are several other (macro style) calls to the Peripheral UART configuration macros in the sample that will throw the same compiler error.
Future versions of the application note, and/or the SDK source file will fix this problem officially. In the interim, you can solve it yourself by adding:
#define REG32(x) *((volatile UINT32*)(x))
to the top of the file: ~include/Drivers/puart.h
just before the
#define UART_REG REG32
Show Less