⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
vineeshvs
Offline
Last seen:3 years 6 months ago
加入:2017-09-14 14:04
蓝牙程序

Hi
I want to burn BLE programs in DA14580DEVKT-B board, I tried it through tera term as like blinky prgram which is mentioned in the manual but I failed to do the same with bluetooth program.
I am using DSPS software (android) for the bluetooth connection, app not showing any device. guide me for BLE program.

Device:
MT_dialog
Offline
Last seen:2 months 1 week ago
工作人员
加入:2015-06-08 11:34
Hi vineeshvs,

Hi vineeshvs,

There are two ways to program the 580, you can either use the JTAG interface or the UART (where the bootloader will copy the image to the sysram). So in order to do so you will have to use either keil or the Smart Snippets tool. I dont quite get where the Tera Term gets involved since, i dont think that any of the manuals indicates to use tera term in order to download code to the 580. As far as i know the tera term is used in order to get the data printed from the blinky example. Regarding downloading the DSPS what you need to do in order to download it to the sysram is to just compile it via keil and just hit the debug button in order to download it via JTAG.

Thanks MT_dialog

vineeshvs
Offline
Last seen:3 years 6 months ago
加入:2017-09-14 14:04
I am programming board using

I am programming board using JTAG, but giving problem while the bluetooth program can u guide me for this.

MT_dialog
Offline
Last seen:2 months 1 week ago
工作人员
加入:2015-06-08 11:34
Hi vineeshvs,

Hi vineeshvs,

Since you ve got a basic kit checking via the power profiler its not possible, so please have the device in debug mode and check if the device doesn't end up in a NMI or a hardfault handler. Also be aware that the DSPS android application will only detect a device that is advertising with the DSPS profile adv data in its advertising string (from the reference designs and demos the only application that does that is the DSPS reference design). So in please try to locate the device via a generic android application.

Thanks MT_dialog