A new Jlink related document has been released (AN-B-052:DA1458x/68x Development Kit Jlink interface) regarding some malfunctions that have been observed with dialog's development kits due to the automated update procedure of the Jlink driver. The document is located under the 58x/68x application notes pages.
I have custom DA14683 boards and got problem about set DA14683(AQFN) USB pin P1_1 & P2_2 as SPI MOSI & MISO pin.
For pcb layout issue, my custom board need to setup P1_1(USB pin) & P2_2(USB pin) as SPI MOSI & MISO pin.
I had trace SPI MOSI & MISO signal output and input by oscilloscope. It can trace waveform to verify hardware is work.
But I can't get any data from SPI read function.
I am setting up a new Linux Ubuntu 18 install with SmartSnippets. I followed the directions here: https://www.dialog-semiconductor.com/sites/default/files/user_manual_um-...
I have the SDK installed and extracted in the same directory as I have selected as my workspace.
I have bought a DA14683 devkit pro to use its mesh functionalities.
On this webpage (https://www.dialog-semiconductor.com/products/smartbond-bluetooth-mesh-sdk) there is a link to request (by email) the mesh SDK.
I have sent an email (3rd June) but have received no niews since then.
Could anyone tell me how I can have acces to the mesh SDK ?
Thank you in advance.
I've written a tiny program which toggles an LED for the DA14683 Pro Development Kit. The program is running from the RAM. When I upload this program manually (without the IDE) this also works fine.
When I upload the exact same program (with the exact same debugger) to our board (an LED is also at P1/5) the CPU always get stuck in the ROM at address 0x07f01dfc (which is a loop onto itself). Maybe this is the "Wait Forever" part of the boot sequence.
i wonder what will happen when i write too many times into VES. For example, assuming VES partition_entry_size / AD_NVMS_VES_MULTIPLIER = 128 / 8 = 16 kBytes. All space will be taken after write 16kB data into it for 8 times. What if i write more than 8 times? shall i erase whole VES 128kB flash before writing the 9th 16kB?
我們依據 DA14683 development kit Pro電路重新設計 DA14683 電路板，在更新 firmware遇到問題.
我們使用 DA14683 development kit Pro 作為 JTAG工具，並對以下接點連線
DA14683 development kit Pro --> 我們的DA14683 電路板
J3-SWCLK/ADC7/P2_4 - > SW_CLK pin of custom board.
J3-SWDIO/ADC4/P0_6 - > SWDIO pin of custom board.
J4-ADC0/P1_2 - > UART_TX of custom board.
J3-P2_3 - > UART_RX of custom board.
I use custom board on chip DA14682. My board use USB only for charge lion battery, USB line D+ and D- not used.
Charging via 5v adapter. In this case, the charging current is not more than 90 mA. Is it possible to increase the charge current in this case?