Differences

This shows you the differences between two versions of the page.

--- nblocks:n-dap [2019/05/01 11:50]
engineer
+++ nblocks:n-dap [2020/01/23 06:47] (current)
engineer
@@ Line 1: / Line 1: @@
-<WRAP  no_pdf hide>
+====== n-DAP ======
-  *<todo #engineer:2017-10-31>Update n-DAP photo</todo>
+~~CLOSETOC~~
-  *<todo #engineer:2017-12-17>Update n-DAP pinout photo: P0.17->P0.22 ADC0; P0.16->P0.12 ADC1; 3.3V->3.3V-OUT; PIN4->5V-FROM-USB-OUT </todo>
+<WRAP right 220px nblock smaller round :en>
-  *<todo #engineer:2017-12-17>Move pinout spreadsheet to pcb repository </todo>
-  *<todo #engineer:2018-01-02>Add photo of assembled boards </todo>
-  *<todo #engineer:2017-12-17>Add block-diagram for CMSIS-DAP programming </todo>
-  * <todo @Manuel> Review, propose updates </todo>
-  * <todo @Nikos> Find and promote capability to be used as DAP for STM32 </todo>
-  * <todo @Faizan> Rework and introduce a Template </todo>
-  * <todo > New board picture with arrows to buttons, ledes, connector </todo>
-  * <todo  #faizan:2019-04-26> Move the target programing diagram lower </todo>
-  * <todo >Add a picture in perspective </todo>
-~~TODOLIST ns:nblocks:n-dap completed:no~~
-</WRAP>
-<WRAP right 190px nblock  box round :en>
 <WRAP centeralign>//**n-DAP**// </WRAP>
-<WRAP centeralign>{{n-dap-v3-orthographic.jpg?100}}</WRAP>
+{{:nblocks:n-dap-10b.jpg}}
 <WRAP centeralign>mbed enable board </WRAP>
 | License        | GPL 2.0 |
@@ Line 35: / Line 13: @@
 </WRAP>
-====== n-DAP ======
 n-DAP is an mbed-enabled development board from the n-Blocks family, with a reduced form factor.
-<WRAP centeralign>{{:nblocks:n-dap-12.jpg?200|}}</WRAP>
+<WRAP centeralign>{{:nblocks:n-dap-3d.png?400|}}</WRAP>
 ===== Overview =====
 The n-DAP-mbed enabled board had been designed by Nimbus Research Center for users to quickly design and develop next generation Internet of things (IoT) applications. The board can facilitate USB drag and drop firmware programming of ARM based CPU boards. It comes with the NXP Semiconductor's LPC11U35 MCU which belongs to the enhanced line of LPC11U3x, ARM-Cortex M0 based, low-cost 32-bit MCU family. The LPC11U35 operate at CPU frequencies of up to 50 MHz and brings unparalleled design flexibility and seamless integration to today’s prototyping and development solutions. The board provides access to the CPUs, ADC, UART and I2C pins which allow the user to use it as a stand alone development board when programmed with custom firmware.
 ===DAP interface===
-The n-DAP [if flashed with a binary image] behaves as a USB to JTAG/SWD bridge between the computer and target's debug access port, using the ARM CMSIS DAP for user friendly programming and debugging. It enables firmware development for n-Blocks boards using the ARM mbed platform and can also be used with industry standard tools such as Keil and IAR.
+The n-DAP (if flashed with a binary image) behaves as a USB to JTAG/SWD bridge between the computer and target's debug access port, using the ARM CMSIS DAP for user friendly programming and debugging. It enables firmware development for n-Blocks boards using the ARM mbed platform and can also be used with industry standard tools such as Keil and IAR.
 The CMSIS-DAP Interface Firmware provides:
@@ Line 56: / Line 35: @@
 ===== MCU Features ====
+<WRAP left 600px  :en>
   * ARM Cortex-M0 processor
   * 50 MHz max CPU frequency
@@ Line 65: / Line 45: @@
   * Internal low-power, low-frequency WatchDog Oscillator
   * 54 GPIOs with configurable pull-up/pull-down resistors
+</WRAP>
   * 8 GPIOs can be selected as edge and level sensitive interrupt sources
   * Programmable WatchDog Timer with a dedicated internal WatchDog Oscillator (WDO)
@@ Line 100: / Line 81: @@
 =====Board Pinout=====
- The board has 12 pins, 6 for each side, If the board is used as SWD interface,  only 3 pins for signals and 2 pins for power are needed\\
+ The board has 12 pins, 6 for each side, If the board is used as SWD interface,  only 3 pins for signals and 2 pins for power are needed.\\
 {{:nblocks:n-dap-7.jpg?1000|}}
@@ Line 120: / Line 101: @@
 =====Getting Started=====
   *  Use the USB lead to connect your mbed to a PC
   *  The red LED will be on, indicating it has power
   *  Press the buttons together (SW4 +SW3).Release the button SW4
   *  Release the button SW3, the CPU would be in ISP mode and appears as Disk with name '''"CRP DISABLD"'''//  //
- {{:nblocks:n-dap-4.jpg?|}}
   * If the CMSIS-DAP (named also mbed_HDK) is programmed, then after reset n-DAP appears as a disk with the mame ''MBED''//  //
 {{:nblocks:n-dap-18.jpg?150|}}
@@ Line 142: / Line 117: @@
 ====Blink example with mbed-CLI====
-  * Check the working target setup// //
+<todo @Nikos> add the code here </todo>
+  * Check the working target setup
 {{:nblocks:mbed-cli-1.jpg?400|}}// //
-  * Compile// //
+  * Compile
 {{:nblocks:mbed-cli-2.jpg?400|}}// //
-  * Remove previous firmware from CPU flash by deleting the file '''firmware.bin'''//  //
+  * Remove previous firmware from CPU flash by deleting the file '''firmware.bin'''// //
 {{:nblocks:fw.jpg?600|}}
-  ***Make sure the folder is empty**, if not then the device can not be programmed//  //
+  ***Make sure the folder is empty**, if not then the device can not be programmed
+  * Drag-drop the new compiled .bin file to the mbed board. It should appear as **firmware.bin**
-  * Drag-drop the new compiled .bin file to the mbed board. It should appear as **firmware.bin**
 \\
@@ Line 170: / Line 142: @@
 ===DAPLink===
   * [[https://os.mbed.com/handbook/DAPLink]]
+// //
+\\
-Link to pre-build image of some targets programmed using n-DAP
+=====Downloads=====
 ===LPC1768/LPC812===
   *[[https://developer.mbed.org/users/chalikias/code/mbed-HDK/| LPC11U35-Firmware for communicating with LPC1768]] (Does not create virtual serial port)
@@ Line 194: / Line 170: @@
+\\

nblocksWiki

User Tools

Site Tools

Differences

Page Tools