6fae9a1aedbd6ffd9064c758b9f635854664cad3
Chip-dat/chip-dat.md
| ... | ... | @@ -42,7 +42,7 @@ from a to z |
| 42 | 42 | |
| 43 | 43 | - [[NXP-dat]] - [[PCA9685-dat]] - [[PCF8574-dat]] - [[i.MX6ULL-dat]] |
| 44 | 44 | |
| 45 | -- [[nordic-dat]] - [[nrf52840-dat]] - [[nrf52840-mod-dat]] |
|
| 45 | +- [[nordic-dat]] - [[nrf52840-dat]] - [[nrf52840-mod-dat]] - [[nrf52832-dat]] |
|
| 46 | 46 | |
| 47 | 47 | - [[mediatek-dat]] - [[MT7688-dat]] - [[MT7628-dat]] |
| 48 | 48 | |
| ... | ... | @@ -57,7 +57,7 @@ from a to z |
| 57 | 57 | |
| 58 | 58 | - [[raspberry-pi-dat]] |
| 59 | 59 | |
| 60 | -- [[Renesas-dat]] - [[DA14585-dat]] |
|
| 60 | +- [[Renesas-dat]] - [[dialog-dat]] - [[DA14585-dat]] |
|
| 61 | 61 | |
| 62 | 62 | - [[ST-dat]] - [[STM32-dat]] - [[STM32-HDK-dat]] - [[STM32-SDK-dat]] |
| 63 | 63 |
Chip-dat/renesas-dat/da14585-dat/2025-09-24-15-44-18.png
| ... | ... | Binary files /dev/null and b/Chip-dat/renesas-dat/da14585-dat/2025-09-24-15-44-18.png differ |
Chip-dat/renesas-dat/da14585-dat/da14585-dat.md
| ... | ... | @@ -1,4 +1,3 @@ |
| 1 | - |
|
| 2 | 1 | # da14585-dat |
| 3 | 2 | |
| 4 | 3 | |
| ... | ... | @@ -22,6 +21,42 @@ |
| 22 | 21 | |
| 23 | 22 |  |
| 24 | 23 | |
| 24 | +tool needed: - [[MDK-ARM-dat]] - [[JLINK-dat]] - [[SmartSnippets-Toolbox-dat]] |
|
| 25 | + |
|
| 26 | + |
|
| 27 | +optional new tools - [[renesas-dat]] |
|
| 28 | + |
|
| 29 | + |
|
| 30 | +wiring == |
|
| 31 | + |
|
| 32 | +Connect the 3V, GND, SWCLK, and SWDIO pins on the DA14585 development board to the J-Link programmer. |
|
| 33 | + |
|
| 34 | +There are several ways to run firmware on the DA14585: |
|
| 35 | + |
|
| 36 | +1. Use a computer to download the firmware into the chip's internal RAM for execution, but the firmware will be lost when power is removed. |
|
| 37 | + |
|
| 38 | +2. Connect external flash to the DA14585. Use a computer to program the firmware into the FLASH. When the chip is powered on, it will read the firmware from flash into RAM for execution. - [[flash-dat]] |
|
| 39 | + |
|
| 40 | +3. Use a computer to program the firmware into the chip's internal OTP, but OTP can only be programmed once, so it is generally used in the final stage of project development. - [[OTP-dat]] |
|
| 41 | + |
|
| 42 | +4. Connect the DA14585 to an external MCU via UART. The 585's firmware is stored in the MCU, and the MCU writes the firmware into the 585's RAM and runs it according to a specific timing sequence. |
|
| 43 | + |
|
| 44 | + |
|
| 45 | +### Configure flash pins |
|
| 46 | + |
|
| 47 | +Why do you need to configure the FLASH pins for programming? Here is a brief explanation, as shown in the figure below. This is because the DA14585 chip has 64KB of OTP memory inside, which means that if you program the chip, you can only do it once. During development, you inevitably need to debug and program repeatedly. How do you solve this? |
|
| 48 | + |
|
| 49 | + |
|
| 50 | + |
|
| 51 | +Usually, a FLASH chip is included. During the debugging phase, code is programmed into the FLASH, allowing for repeated debugging and programming. The SDK also provides library files for booting the chip from FLASH. You just need to configure the relevant macro definitions, which is very convenient, as shown in the figure below. Once the code is stable and the product is ready for mass production, the FLASH can be removed, and the code can be programmed into the OTP memory. (PS: This is probably why the DA14585 is cheaper than Nordic.) |
|
| 52 | + |
|
| 53 | + |
|
| 54 | +## SDK |
|
| 55 | + |
|
| 56 | +examples |
|
| 57 | + |
|
| 58 | +6.0.12.1020.2\SDK\6.0.12.1020.2\projects\target_apps\ble_examples\prox_reporter\Keil_5 |
|
| 59 | + |
|
| 25 | 60 | ## info |
| 26 | 61 | |
| 27 | 62 | SmartBond™ Bluetooth 5.0 SoC with Audio Interface |
Chip-dat/renesas-dat/renesas-dat.md
| ... | ... | @@ -24,9 +24,17 @@ DA14580 is selected by Xiaomi Bracelet. DA14580 is the world's smallest, lowest |
| 24 | 24 | |
| 25 | 25 | ## tools |
| 26 | 26 | |
| 27 | +- [[SmartSnippets-Toolbox-dat]] - [[E2-studio-dat]] |
|
| 28 | + |
|
| 29 | +- [[SDK-dat]] |
|
| 30 | + |
|
| 27 | 31 | Renesas Flash Programmer V3.20.00 |
| 28 | 32 | |
| 29 | 33 |  |
| 30 | 34 | |
| 31 | 35 | |
| 32 | 36 | |
| 37 | + |
|
| 38 | +## ref |
|
| 39 | + |
|
| 40 | +- [[chip-dat]] |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-42-27.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-42-27.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-43-19.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-43-19.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-45-11.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-45-11.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-46-23.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-46-23.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-04.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-04.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-33.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-33.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-59.png
| ... | ... | Binary files /dev/null and b/SDK-dat/SmartSnippets-Toolbox-dat/2025-09-24-15-47-59.png differ |
SDK-dat/SmartSnippets-Toolbox-dat/SmartSnippets-Toolbox-dat.md
| ... | ... | @@ -0,0 +1,36 @@ |
| 1 | +# SmartSnippets-Toolbox-dat |
|
| 2 | + |
|
| 3 | + |
|
| 4 | + |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +4. Click "Open" to enter the configuration interface. Select the "Board Setup" menu, and configure the serial port and SPI FLASH pins in the programming tool according to the schematic (if using I2C EEPROM, select the I2C pins). |
|
| 8 | + |
|
| 9 | + |
|
| 10 | + |
|
| 11 | +Click "Board Setup" and configure according to the steps below. |
|
| 12 | + |
|
| 13 | + |
|
| 14 | + |
|
| 15 | +Click "SPI Flash/EEPROM" and configure according to the steps below. |
|
| 16 | + |
|
| 17 | + |
|
| 18 | + |
|
| 19 | +7. After the board connects successfully, click "Erase" to erase the Flash once. |
|
| 20 | + |
|
| 21 | + |
|
| 22 | + |
|
| 23 | +Next, import the hex firmware to be programmed. Click "Browse", then select the path of the firmware to be programmed, select it, and click "Open". |
|
| 24 | + |
|
| 25 | + |
|
| 26 | + |
|
| 27 | +After programming is complete, power cycle the development board. Open the nRF Connect APP to scan for the device, and you should be able to find it. |
|
| 28 | + |
|
| 29 | + |
|
| 30 | + |
|
| 31 | + |
|
| 32 | +## ref |
|
| 33 | + |
|
| 34 | +- [[renesas-dat]] |
|
| 35 | + |
|
| 36 | +- [[SDK-dat]] |
|
| ... | ... | \ No newline at end of file |
Tech-dat/memory-dat/OTP-dat/OTP-dat.md
| ... | ... | @@ -0,0 +1,20 @@ |
| 1 | + |
|
| 2 | +# OTP-dat |
|
| 3 | + |
|
| 4 | +- [[DA14585-dat]] |
|
| 5 | + |
|
| 6 | +OTP (One-Time Programmable) memory is a type of non-volatile memory that can be programmed only once. It is commonly used in microcontrollers and other integrated circuits for storing firmware or configuration data that does not need to be changed after initial programming. |
|
| 7 | + |
|
| 8 | +features of OTP memory: |
|
| 9 | + |
|
| 10 | +- Non-volatile: Retains data even when power is removed. |
|
| 11 | +- One-time programmable: Once data is written, it cannot be altered or erased. |
|
| 12 | +- Cost-effective: Generally cheaper than other types of non-volatile memory like EEPROM or Flash. |
|
| 13 | +- Limited capacity: Typically has a smaller storage capacity compared to other memory types. |
|
| 14 | +- Fast access times: Similar to other non-volatile memory types. |
|
| 15 | + |
|
| 16 | + |
|
| 17 | + |
|
| 18 | +## ref |
|
| 19 | + |
|
| 20 | +- [[memory-dat]] |
|
| ... | ... | \ No newline at end of file |