Hi,
I'm new for developing the DA14580devkt-b.
After installation of uVision + J-link, I always failed to load code to device
Here are some questions that I would like to have your comment:
1. while opening the sample project provided in SDK 'DA14580_581_SDK_3.0.8.0', it prompts for the conversion choice, which one shall I select? I choose 'Migrate to Device Pack', it will then convert project file from version 4 to 5. But it turned out an error report 'Device(s) not found' which showing that 'ARM:Cortex-M0' is not found in available Device Family Packs. I choose 'Yes' to confirm the migration to Pack device(s). Then I choose 'ARM Cortex M0' in the selection tab of CPU.
2. In the 'option for target' setting of uVision, the tab 'Target' is not consistent to the Document 'UM-B-025 - DA14580_581 Bluetooth® Smart Development Kit - Basic V2.0', the IROM1 and IRAM1 addressing is not the same. Also, the Xtal setting of CPU is 12.0, but 16.0 is in the screen shot provided from document.
Is there any guide or manual for the new uVision?
Hello Hardy.chen,
which version of uVision have you installed ? we are having some challenges with the Keil tool - once its set-up right, it works just fine, but can be a challenge to get to that point.
BR JE_Dialog
Hi,
我用uVision 5可以下载从她的e 'http://www2.keil.com/mdk5/install'
I'm presuming you're running 5.14 ? I have 5.11 . Later tongiht, i will upgrade to 5.14 and see if i can replicate the problem.
BR JE_Dialog.
Hi,
我只是下载5.14,安装,让它更新ll the missing packs, and then started. It found the DA14580 just fine. Question 2 will not be solved until you have the right device, so we need to focus on that first.
Have you manually tried to update all of the device packs ?
BR JE_Dialog
I suppose that regrading all of the device packs is referring to 'Pack Installer'.
In the 'Pack Installer', the pack 'ARM:CMSIS' is 'Up to date' and at tab 'Devices' on the right panel, I don't see any 'Dialog Semiconductor' presented.
(Sorry, I can't find a way to upload the snapshot to this post.)
I then checked the device database from 'File -> Device Database', I can see DA14580 presented in 'Dialog Semiconductor'
Description as below:
Cortex M-0 based Bluetooth Low Energy (BTLE) controller
32 kByte OTP memory, 42 kByte System rAM, 4 kByte retention RAM, 82 kByte ROM
CPU=CLOCK(16000000) CPUTYPE("Cortex-M0") ESEL ELITTLE
MON=SARMCM3.DLL("") TARMCM1.DLL("-pCM0")
SIM=SARMCM3.DLL("") DARMCM1.DLL("-pCM0")
SVD=SFD\Dialog\DA14580\DA14580.sfr
Anyway, I still can't choose the right device from the 'Options for Target' in which the Device Database selection bar is disabled.
When I open the sample 'proxy_reporter' from SDK, the uVision will prompt to ask for the migration with 2 options 1) Migrate to Device Pack, 2) Install Legacy Support. If I choose option 1), it will turn to the error message 'The following Device(s) could not be found in available Device Family Packs: -ARM:Cortex-M0, Do you want to migrate to use Pack device(s)?
I am the same problem, any ideas about that ?
Hi,
I have the same problem with my DA14580DEVKT. I followed all steps of the pdf "UM_B_025 DA14580_581_Bluetooth_Smart_developement_kit-Basic V2.2".
I'm using Keil µVision 5.14. In pack installer, I have selected ARM --> ARM Cortex M0 --> ARMCM0 and I have installed ARM::CMSIS and Keil::MDK-Middleware.
Now the ARMCM0 is in green.
I try to use the "Blinky_UART_code" example. As hardy.chen explains, when I open the project for the first time, Keil asks me to convert it.
Now in "Options for Target" I'm able to select the JLINK for debugging and I see the right SN.
I can build the project but when I try to start a debug session or download code, I have an error :
No Algorithm found for: 00000000H - 00000447H
Erase skipped!
Error: Flash Download failed - "Cortex-M0"
I assume this problem occurs because I'm not able to select the right device in the pack installer ?
Hello mbiron,
I assume that you clicked the "Download" button which is to download code to flash memory. you may need press the button of "start/stop debug session" or CTRL+F5 to enter debug mode and run the project.
BR, MH_Dialog
Hi,
Thank you for your quick answer.
I have the same error when I start the debug session. It seems that µVision did the same thing when I click on "Download" or "Start Debug Session".
EDIT: I'm able to launch the "blinky_arrived" demo using SmartSnippets (Booter section). But this example still doesn't work with µVision Debug Mode :
No Algorithm found for: 20000000H - 200012EBH
Erase skipped!
Error: Flash Download failed - "Cortex-M0"
我只是下载5.14,安装,让它更新ll the missing packs, and then started. It found the DA14580 just fine.
How have you managed to select "Dialog Semiconductor" in your Pack Installer ?
This is mine :http://www.hostingpics.net/viewer.php?id=970250Sanstitre.jpg
I have the same as yours. How did you add "Dialog Semiconductor" in your Pack Installer ?
Thanks for your answer...
Hi again,
I finally found the solution in the "UM-B-014_DA14580_581 Bluetooth Smart Development Kit - Expert_v1.5_0.pdf". Because µVision selects "Use Target Driver for flash programming" by default, it tries to flash the target when you start a Debug session.
This option is found in Options for Target / Utilities.
You just need to select "Use External Tool for Flash Programming" and don't specify any command and that's it!
I don't know why this information is missing in the basic development kit user guide.
thakns for letting us know you got it to work : I'll ask the documentation team to update the docs. BR JE_Dialog
I am facing problem when debugging Dialog Beacon µVision project with Error Message :
No Cortex-M SW Device Found.
As check under Option for Target >> Debug >> Use J-LINK/J-TRACE Cortex>> Setting>> SW Device >> Cannot Add/Delete/Update option Grey Off
Base on the UM-B-034 User Manual, Page 25 Section 6.17 the SW Device listed are 0x0BB11477 ARM Core Sight SW-DP.
Please help to advise how add SW Device?
Hi ngchinping,
Your device should be recognized automatically by keil when you switch the from JTAG to SW option. For some reason keil doesn't seems that isn't able to "see" the dev kit. Can you please connect the dev kit and issue a reset to the board, also you might want to check your jlink drivers installation.
Thanks MT_dialog