Hi Dialog,
Have ported a DA14585 QFN40 Custom board to a Da1458x Development kit pro. Device properly detected through smart snippet tool on jtag dongle, but everytime i try to run the barebone project
I usually get errors below. Same error encountered using a jlink ultra+ directly connected to the jtag ports of the custom board. Can the interference/crosstalk on the 16MHz crytal oscillator affect these errors, knowing that 16MHz crystal is so sensitive to external influences based on the application note AN-B-009 ?Attached is the system schematic of the custom board where P1_2 and P1_3 are utilized for other applications.
But just to satisfy the crystal oscillator layout guidelines, have modified the custom board porting P1_2 and P1_3 to ground to improve the oscillation. Running the barebone project still encountered the same error below.
Any other factors for these errors?
BLE IC = DA14585 00000
16MHz crystal = 7M-16.000MEEQ-T
Vdc_dc = 1.6V~1.8V
**JLink Warning: CPU could not be halted
***JLink Error: Can not read register 15 (R15) while CPU is running
***JLink Error: Can not read register 16 (XPSR) while CPU is running
***JLink Error: Can not read register 0 (R0) while CPU is running
***JLink Error: Can not read register 1 (R1) while CPU is running
***JLink Error: Can not read register 2 (R2) while CPU is running
***JLink Error: Can not read register 3 (R3) while CPU is running
***JLink Error: Can not read register 4 (R4) while CPU is running
***JLink Error: Can not read register 5 (R5) while CPU is running
* * * JLink错误:无法读取寄存器6 (R6)CPU is running
***JLink Error: Can not read register 7 (R7) while CPU is running
***JLink Error: Can not read register 8 (R8) while CPU is running
***JLink Error: Can not read register 9 (R9) while CPU is running
***JLink Error: Can not read register 10 (R10) while CPU is running
***JLink Error: Can not read register 11 (R11) while CPU is running
***JLink Error: Can not read register 12 (R12) while CPU is running
***JLink Error: Can not read register 13 (R13) while CPU is running
***JLink Error: Can not read register 14 (R14) while CPU is running
***JLink Error: Can not read register 15 (R15) while CPU is running
***JLink Error: Can not read register 16 (XPSR) while CPU is running
***JLink Error: Can not read register 17 (MSP) while CPU is running
***JLink Error: Can not read register 18 (PSP) while CPU is running
***JLink Error: Can not read register 20 (CFBP) while CPU is running
Hi R3CTOR,
No, the crosstalk between the XTAL16 and the P12 and P13 wont produce this kind of issue, usually when toggling those pins in high frequency the device will operate but you wont be able to properly transmt during advertising or connect. The errors that you get are because apparently at somepoint the jlink is loosing connection with the device or is not able to connect at all or it connects and then the device for some reason reboots and the debugger disconnects. Are you using the Jlink from the pro dev kit ? You mentioned that you downloaded code using Smart Snippets have you connected using the JTAG or the UART interface ?
Thanks MT_dialog
Hi MT_dialog,
Is it related to the jlink debugger used for the connection issue? Compatibility issue? I'm using a jlink ultra + debugger to a custom board and the development kit is using a Jlink Lite ARM debugger. If using the jlink from the pro dev kit to a custom board, is there any other configuration needed? Using smart snippets I can detect the connected device but error running the barebone project.
JUst an observation for the barebone project, is there a compatibility issue for various DA14585 BLE IC? The development kit can run using SDK(6.0.2) but not on SDK(6.0.4) and SDK (6.0.6).
BLE IC for Custom Board = DA14585 00000
Hi R3CTOR,
As mentioned above the messages that keil reports are because the jlink is disconnected from the device, also as mentioned in this posthttps://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bl...i am not able to verify that the jlink that you are using will be fully compatible with the 585 or there is need for additional configuration for keil in order to work (which i suppose that it should be compatible but i am not able to verify it). Regarding the jlink that comes with the pro dev kit, yes you can use that jlink just by hooking the TMS and TCK pins to the SWDIO and SWCLK pins of your custom board. So are you using the jlink from the dev kit and you get the above messages or the ultra+debugger ?
Regarding the compatibility issue that you mention, currently on the market there is only one version of the 585 and this is the AC, but also you might run on an older version of the 585 which is the AB version. The AB version is only compatible with the 6.0.2 SDK version, if you try to run the SDK 6.0.4 or 6.0.6 on a AB silicon the code will end up in a hardfault the same stands for the opposite, meaning running a SDK 6.0.2 on an AC version. The only way to distinquish those two versions is from the markings on the package it self, so AB silicon will indicate DA14585 AB000 and AC silicon will indicate DA14585 00000.
Thanks MT_dialog
Hi MT_ Dialog,
Thank you for the support, custom board already working. It is more of assembly issue found, grounding related for BLE IC substrate...