Hi,
Our design is to have and external MCU and interface with BLE through UART. But while waiting for the form factor, I'm developing using the BASIC kit.
My question is can i use the Tera Term to simulate as external MCU? if yes, do you have any sample codes on this scenario?
I'm currently reading UM-B-017 in which is prefect to our needs and the example project i also tried but didn't fully understand if i did it correct. Could someone please provide some steps on how to try this example on the BASIC kit if possible? Thanks in advance.
But just for FYI, what i did was I compiled those projects with Keil. Then downloaded them using SmartSnippets. Then i tried to use Terminal tab and clicked Start Terminal, both app provided a similar output, it give some garbage data on the terminal, is this intended? I verified it using Tera Term and still the same. What would be expected for this example?
Btw, do you have any demo app for Android for data streaming or any profile? Is it possible if we could use that app as for reference or debugging purpose?
Thanks and looking forward to hear from you.
BR,
Geo
Hi Geo,
You can simply use a PC program to simulate an external MCU.
UM-B-017 is surely an interesting document, but I would suggest to have a look of
UM-B-010 User Manual : Proximity Example in Integrated and External Processor Solution1.1
Hi WT,
Thanks for you reply and yes i'm now reading UM-B-010. I attempt to try the proximity sample on my BASIC kit but it seems i cannot detect any BLE signal, anything that i missed here? I use the reporter_fh project and i set the Memory areas stated on UM-B-025 and when i start the debugger and using a simple Android app just to check for BLE signals, i cannot find the device. Btw do we need to download the BLE stack to the ROM or is it already included during debug?
OK it was wrong to follow the Memory setup in UM-B-025 and now i was able to run throughput_eval_peripheral_fh. But when i went back with reporter_fh, still wont show on my BLE phone app, should the reporter advertise right?
Geo,
You need to stop the debugger or disable both sleep modes in the da14580_config.h file of the project.
I hope that helps.
Hi MHv,
Yes! It works now, i undefine the sleep modes, thanks!!
BR,
geo
Hi Geo,
Glad to hear that.
Sleep mode (both deep sleep and extended sleep) turns the M0 completely off. The debugger has no way to handle this, so turning sleep mode off while you are debugging is crucial. Don't forget to reactivate sleep mode before you make your power consumption measurements or put your device into production (well, unless you have investments in a battery vendor, of course)
Hi MHv,
OK this is noted, will return the sleep configuration once we test power consumption or for device production.
BR,
Geo