Chip-dat/ARM-dat/ARM-dat.md
... ...
@@ -8,6 +8,27 @@
8 8
- [[jlink-dat]] - [[st-link-dat]] - [[dap-link-dat]] - [[CMSIS-DAP-dat]]
9 9
10 10
11
+## protocol / interface
12
+
13
+- [[JTAG-dat]] - [[SWD-dat]]
14
+
15
+
16
+
17
+## framework
18
+
19
+**CMSIS** = **Cortex Microcontroller Software Interface Standard**
20
+
21
+- Developed by **ARM**.
22
+- Provides a **standardized software framework** for Cortex-M microcontrollers.
23
+- Main purposes:
24
+ - Defines a consistent **API** across Cortex-M chips.
25
+ - Supplies **startup code** and core access functions.
26
+ - Provides **DSP library** and **RTOS interface**.
27
+ - Simplifies **portability** of code between different ARM Cortex-M devices.
28
+
29
+👉 In short: CMSIS makes programming Cortex-M chips easier, faster, and more portable.
30
+
31
+
11 32
12 33
13 34
Chip-dat/Dialog-dat/Dialog-dat.md
... ...
@@ -1,6 +0,0 @@
1
-
2
-# Dialog-dat
3
-
4
-DA14580 is selected by Xiaomi Bracelet. DA14580 is the world's smallest, lowest power, and most integrated Bluetooth smart SoC.
5
-
6
-- [[DA14580-dat]]
... ...
\ No newline at end of file
Chip-dat/renesas-dat/Dialog-dat/Dialog-dat.md
... ...
@@ -0,0 +1,7 @@
1
+
2
+# Dialog-dat
3
+
4
+2021年8月31日 — With the transaction now closed, Dialog became a wholly owned subsidiary of [[Renesas-dat]].
5
+
6
+
7
+
Chip-dat/renesas-dat/da14585-dat/da14585-dat.md
... ...
@@ -1,6 +1,10 @@
1 1
2 2
# da14585-dat
3 3
4
+
5
+- [[MDK-ARM-dat]]
6
+
7
+
4 8
## project
5 9
6 10
- [[epaper-dat]]
... ...
@@ -10,7 +14,9 @@
10 14
设计工具 https://epd.eled.top/
11 15
12 16
17
+## functions
13 18
19
+- [[BLE-dat]]
14 20
15 21
## info
16 22
Chip-dat/renesas-dat/renesas-dat.md
... ...
@@ -9,3 +9,13 @@ https://www.renesas.com/en/document/dst/hin202e-hin206e-hin207e-hin208e-hin211e-
9 9
10 10
- [[da14585-dat]]
11 11
12
+- [[dialog-dat]]
13
+
14
+
15
+DA14580 is selected by Xiaomi Bracelet. DA14580 is the world's smallest, lowest power, and most integrated Bluetooth smart SoC.
16
+
17
+- [[DA14580-dat]]
18
+
19
+
20
+
21
+- [[MDK-ARM-dat]]
... ...
\ No newline at end of file
SDK-dat/MDK-ARM-dat/2025-09-23-13-01-15.png
... ...
Binary files /dev/null and b/SDK-dat/MDK-ARM-dat/2025-09-23-13-01-15.png differ
SDK-dat/MDK-ARM-dat/MDK-ARM-dat.md
... ...
@@ -1,19 +1,31 @@
1 1
2 2
# MDK-ARM-dat
3 3
4
-- [[MDK-ARM]]
5 4
6 5
- setup new compiler in KEIL-MDK [[AC5-dat]] - [[AC6-dat]]
7 6
8
-## supported device
9
-
10
-- [[STM32-dat]]
7
+- [[ARM-dat]]
11 8
12
-- [[DA14585-dat]]
13 9
14 10
## programmer
15 11
16
-- [[Jlink-dat]]
12
+- [[Jlink-dat]] - [[MDK-ARM-dat]]
13
+
14
+
15
+- ULINK2/ME Cortex Debugger
16
+- ULINK Pro Cortex Debugger
17
+- ULINKplus Debugger
18
+- CMSIS-DAP Debugger
19
+- J-LINK/J-TRACE Cortex - [[Jlink-dat]]
20
+- Models Cortex-M Debugger
21
+- ST-Link Debugger
22
+- Pemicro Debugger
23
+- NULink Debugger
24
+- SiLabs UDA Debugger
25
+- Altera Blaster Cortex Debugger
26
+- TI XDS Debugger
27
+
28
+
17 29
18 30
## KEIL-MDK
19 31
... ...
@@ -56,11 +68,18 @@ install from official websites
56 68
- D:\Keil_v5\ARM
57 69
- install into "AC5"
58 70
59
-## Supports
71
+
72
+
73
+## supported device
74
+
75
+- [[STM32-dat]]
76
+
77
+- [[DA14585-dat]] == https://s3.eu-central-1.amazonaws.com/lpccs-docs.renesas.com/CMSIS/DialogSemiconductor.DA1458x_DFP.1.1.3.pack == https://www.keil.arm.com/packs/da1458x_dfp-dialogsemiconductor/devices/
60 78
61 79
- [[HDSC-SDK-dat]] - [[STM32-SDK-dat]]
62 80
63 81
Supported Device
82
+
64 83
* https://w.electrodragon.com/w/WCH - CH579
65 84
* https://w.electrodragon.com/w/HDSC - HC32L136
66 85
* https://w.electrodragon.com/w/Nordic - NRF52832
... ...
@@ -68,6 +87,16 @@ Supported Device
68 87
* https://w.electrodragon.com/w/NXP - LPC1100, RT1021
69 88
* https://w.electrodragon.com/w/ARM - Cortex A5 A7 A9
70 89
90
+
91
+
92
+## usage
93
+
94
+setup run-time enviornment
95
+
96
+![](2025-09-23-13-01-15.png)
97
+
98
+
99
+
71 100
## Error log
72 101
73 102
### --locale=english
... ...
@@ -195,4 +224,6 @@ Destination Folder: d:\MDK\Arm\Packs\KeilSTM32F1xx_DFP\2.4.1
195 224
196 225
## ref
197 226
198
-- [[keil]] - [[MDK-ARM]]
... ...
\ No newline at end of file
0
+- [[keil]] - [[MDK-ARM]]
1
+
2
+
SDK-dat/programming-dat/Programmer-dat/JLINK-dat/2025-09-23-13-17-18.png
... ...
Binary files /dev/null and b/SDK-dat/programming-dat/Programmer-dat/JLINK-dat/2025-09-23-13-17-18.png differ
SDK-dat/programming-dat/Programmer-dat/JLINK-dat/2025-09-23-13-24-54.png
... ...
Binary files /dev/null and b/SDK-dat/programming-dat/Programmer-dat/JLINK-dat/2025-09-23-13-24-54.png differ
SDK-dat/programming-dat/Programmer-dat/JLINK-dat/JLINK-dat.md
... ...
@@ -1,12 +1,17 @@
1 1
2 2
# JLINK dat
3 3
4
+
5
+- [[ARM-dat]]
6
+
4 7
- [[DPR1135-dat]]
5 8
6 9
7 10
JLink is a the SEGGER company launched JTAG emulator for ARM core chip to support simulation. IAR EWARM, ADS, KEIL, WINARM, RealView and other integrated development environment with the support all ARM7/ARM9 kernel chip simulation and seamless connectivity through the RDI interface and the integrated development environment, easy to operate, easy to connect, easy to learn, learning to develop ARM the best and most practical development tools.
8 11
9 12
13
+- [[JTAG-dat]] - [[SWD-dat]]
14
+
10 15
## About J-Link
11 16
12 17
... ...
@@ -23,6 +28,73 @@ JLink is a the SEGGER company launched JTAG emulator for ARM core chip to suppor
23 28
24 29
25 30
31
+## supported MCUs
32
+
33
+- ARM7/9/11，
34
+- Cortex-A5/A7/A8/A9，
35
+- Cortex-M0/M1/M3/M4/M7，Cortex-R4，
36
+- Microchip PIC32
37
+- Renesas RX100/RX200/RX610/RX621/RX62N/RX62T/RX630/RX631/RX63N
38
+
39
+
40
+## usage
41
+
42
+![](2025-09-23-13-24-54.png)
43
+
44
+- VOUT is a 3.3V voltage output pin.
45
+- Users can remove the internal shorting jumper of the device to disable the 3.3V output.
46
+- VTREF is the internal voltage reference; this pin must be connected to
47
+
48
+
49
+
50
+## BULK interface
51
+
52
+- [[usb-driver-dat]] - [[serial-dat]]
53
+
54
+![](2025-09-23-13-17-18.png)
55
+
56
+# What is a BULK Interface (USB)?
57
+
58
+A **BULK interface** is a type of **USB transfer mode** defined by the USB specification.
59
+It is used for **large, non-time-critical data transfers** between a USB device and a host.
60
+
61
+---
62
+
63
+## Key Points
64
+
65
+- **Purpose**: Moves large amounts of data reliably, without strict timing.
66
+- **Error Handling**: Each transfer is error-checked (CRC). If errors occur, the host retries.
67
+- **Speed**: Uses all available USB bandwidth that isn’t reserved for other transfers.
68
+- **Transfer Size**:
69
+ - USB 2.0 → up to **64 KB per transfer**, with max **512 bytes per packet** (High-Speed).
70
+ - USB 3.0 → larger packet sizes (up to **1024 bytes**).
71
+- **Scheduling**: Lowest priority compared to isochronous or interrupt transfers.
72
+ The host only sends bulk data when bus time is free.
73
+
74
+---
75
+
76
+## Examples of Devices Using BULK Transfers
77
+- **USB flash drives** (file transfers).
78
+- **Printers** (sending print jobs).
79
+- **Scanners** (image data).
80
+- **Custom devices** (MCU development boards, DA14585 debug/test interfaces, etc.).
81
+
82
+---
83
+
84
+## Comparison with Other USB Transfers
85
+
86
+| Transfer Type | Use Case | Priority | Guaranteed Bandwidth | Error Handling |
87
+|-----------------|------------------------------|----------|----------------------|----------------|
88
+| **Control** | Device configuration (setup) | Highest | Yes | Yes |
89
+| **Isochronous** | Audio/video streaming | High | Yes | No retry |
90
+| **Interrupt** | Small, quick signals (mouse) | Medium | Yes | Yes |
91
+| **Bulk** | Large, non-urgent data | Lowest | No | Yes |
92
+
93
+---
94
+
95
+👉 In short: A **BULK interface** is a **USB data channel** used for transferring large, reliable chunks of data when timing is not critical.
96
+
97
+
26 98
27 99
## ref
28 100
Tech-dat/ARM-dat/SWD-dat/2025-09-23-13-27-22.png
... ...
Binary files /dev/null and b/Tech-dat/ARM-dat/SWD-dat/2025-09-23-13-27-22.png differ
Tech-dat/ARM-dat/SWD-dat/SWD-dat.md
... ...
@@ -11,7 +11,21 @@ https://stm32-base.org/guides/connecting-your-debugger.html
11 11
12 12
![](2024-07-05-17-37-28.png)
13 13
14
+
15
+## wiring
16
+
17
+![](2025-09-23-13-27-22.png)
18
+
19
+供电方式一般有三种：
20
+
21
+- 1，使用5V-supply引脚经过目标板的LDO给McU供电。
22
+- 2，直接将VOUT引I脚连接到MCU的VCC进行供电
23
+- 3，用户也可以选择目标板自带供电。
24
+- 注意：无论那种供电方式，VTREF引I脚都必须连接到MCU的VCC。
25
+
14 26
## Debug
27
+
28
+
15 29
* If SWD Serial-Wire is not enable, add reset line to force enter into debug mode
16 30
17 31
- [[USB-TTL-dat]]
Tech-dat/Interface-dat/Jtag-dat/2025-09-23-13-23-45.png
... ...
Binary files /dev/null and b/Tech-dat/Interface-dat/Jtag-dat/2025-09-23-13-23-45.png differ
Tech-dat/Interface-dat/Jtag-dat/2025-09-23-13-26-03.png
... ...
Binary files /dev/null and b/Tech-dat/Interface-dat/Jtag-dat/2025-09-23-13-26-03.png differ
Tech-dat/Interface-dat/Jtag-dat/Jtag-dat.md
... ...
@@ -9,12 +9,42 @@ Full Jtag Interface
9 9
10 10
![](2024-01-13-17-50-18.png)
11 11
12
+![](2025-09-23-13-23-45.png)
13
+
14
+
15
+- VTref -- VOUT
16
+- nTRST -- GND
17
+- TDI -- GND
18
+- TMS -- GND
19
+- TCK -- GND
20
+- RTCK -- GND
21
+- TDO -- GND
22
+- RESET -- GND
23
+- DBGRQ -- GND
24
+- 5V-Supply -- GND
25
+
26
+## wiring
27
+
28
+![](2025-09-23-13-26-03.png)
29
+
30
+power supply
31
+
32
+供电方式一般有三种：
33
+
34
+- 1，使用5V-supply引脚经过目标板的LDO给McU供电。
35
+- 2，直接将VOUT引I脚连接到MCU的VCC进行供电
36
+- 3，用户也可以选择目标板自带供电。
37
+- 注意：无论那种供电方式，VTREF引I脚都必须连接到MCU的VCC。
38
+
12 39
13 40
14 41
## repo
15 42
43
+
16 44
- JLINK - https://github.com/Edragon/Jlink
17 45
46
+
47
+
18 48
## ref
19 49
20 50
- [OpenOCD](http://openocd.org/)
... ...
\ No newline at end of file
Tech-dat/Interface-dat/USB-dat/USB-driver-dat.md
... ...
@@ -0,0 +1,23 @@
1
+
2
+# USB-driver-dat
3
+
4
+https://github.com/Edragon/git-serial
5
+
6
+
7
+
8
+
9
+## 3. Install with Zadig (if no official driver) for BULK interface devices
10
+
11
+1. Download [Zadig](https://zadig.akeo.ie/).
12
+2. Run it as administrator.
13
+3. In the device list, find your **BULK interface device**.
14
+4. Select driver type:
15
+ - **WinUSB** (recommended for most applications).
16
+ - Or **libusbK/libusb-win32** if required by software.
17
+5. Click **Install Driver** (or **Replace Driver**).
18
+
19
+
20
+
21
+## ref
22
+
23
+- [[USB-dat]]
... ...
\ No newline at end of file
Tech-dat/Interface-dat/USB-dat/usb-dat.md
... ...
@@ -1,9 +1,11 @@
1 1
2 2
# usb-dat
3 3
4
+- [[USB-driver-dat]] - [[libusb-dat]]
5
+
4 6
- [[USB-cable-dat]] - [[USB-ESD-dat]]
5 7
6
-- [[CONN-USB-dat]]
8
+- [[CONN-USB-dat]] - [[conn-dat]]
7 9
8 10
- [[USB-STM32-dat]]
9 11