Hi All,
我’ve spent a few hours today trying to get the proximity reporter/monitor example project up and running. I’ve been loosely following the UM-B-010 guide along with the UM-B-014, but it doesn’t seem like it should be too complicated.
我’ve tried the following pairs:
reporter_fe_usb\fe_usb_proxr.uvproj as theReporteron theUSB Dongle
monitor_fe\fe_proxm_sdk.uvproj as theMonitoron theDK
reporter_fe\fe_proxr.uvproj as theReporteron theDK
monitor_fe_usb\fe_usb_proxm_sdk.uvproj as theMonitoron theUSB Dongle
我n both cases, I was able to reliably get the monitor functioning properly and communicating with the PC app. I was able to scan for devices, and the monitor was able to find a few BLE devices sitting around the office.
However, in both cases, the reporter failed to show up when scanning with the monitor. The reporter code appeared to be running, and I executed it and set up the project identically to the monitor. However, no listing for the reporter showed up in the monitor. I should mention nothing showed up in the terminal for the reporter as well, but I'm pretty sure nothing is supposed to. Correct me if I'm wrong there.
我don’t think it’s an issue with my keil settings or with loading the code, as I was able to perform both actions successfully on both the dongle and the DK using the monitor app.
Do you have any thoughts? Could it be a problem with how the reporter is ‘reporting’, causing it to not show up? Is there anything else I have to change in code/project settings that is different between the two apps?
我am running both projects by loading code with the debugger, then immediately exiting the debugger.
Let me know, I appreciate the help.
This is on the latest version of both Keil_v5 and the SDK (3.0.6).
Thanks!
Andrew
Just an update, I recently tried with the reporter_fh app on both the dongle and the DK. I then tried to use the BlueLoupe app for android to scan for the device, and the app was not able to find either.
Let me know if you guys have any thoughts.
Another update, I've determined the problem.
The GPIO initialization were causing assembly breakpoints to halt the code. I had to define "GPIO_DRV_PIN_ALLOC_MON_DISABLED" to disable the assembly breakpoints, and this allowed the code to run properly.
我t appears as though the code in the SDK is not initializing the GPIO's correctly and is causing the breakpoints to trip. However, I have not fully investigated the root cause.
This was fresh code from the SDK, so I believe the SDK code is technically broken as it sits.
Andrew
Hello Andrew, I believe one of the US FAE team has been discussing with you. I will check with the software team also and feedabck your findings.. It looks like you have the proximity app working and therefore i will close the ticket.
Thanks &BR
JE _Dialog
JE_Dialog,
我should mention that the above post about the fix was actually in reference to the reporter_fh app only. I still have not gotten the reporter_fe app to work.
Thanks!
Andrew