Prduct Details The EVAL-ADICUP360 is an Arduin and PMOD cmpatible frm factr develpment bard. The bard uses an pen surce Eclipse based Interactive Develpment Envirnment (IDE) which can be dwnladed free f charge. The platfrm cntains many hardware and sftware example prjects, t make it easier fr custmers t prttype/create systems and slutins using the cmplete ecsystem prvided. The EVAL-ADICUP360 uses the ADuCM360 Arm Crtex-M3 prcessr as the main device n bard. It has integrated dual 24-bit sigma delta cnverters n chip, which make it extremely flexible fr bth analg and digital applicatin. Tl Chain Setup User Guide This page prvides detailed infrmatin abut using the ADuCM360 custmized Eclipse IDE, in particular, the prcess f imprting, building, debugging, and creating user applicatins fr the ADuCM360 micrcntrller. This page will utline:
1. Hw t imprt existing prjects int yur wrkspace 2. Hw t build the.elf files, fr prgramming the ADuCM360 3. Hw t cnfigure the debug sessin fr a particular user applicatin 4. Hw t start a debug sessin 5. Hw t create a new prject Wrkspace and Prjects The wrkspace is a flder where Eclipse can access lcal cpies f user applicatin prjects. When starting Eclipse, a prmpt will ask yu fr a lcatin f this flder. This is the lcatin where all the ADuCM360 user applicatins will be stred. Using the Tl Chain The instructins belw have been tested in Windws XP and Windws 7, n bth 32-/64-bit machines. Imprting a Prject There are 2 methds fr imprting existing prgrams: Examples that cme with the installer package. Examples which are in ur GIT repsitry (mst up t date cntent).
Only ne methd is needed t get started with the EVAL-ADICUP360. Hw t Imprt Existing Prjects within the Installer Package 1. Frm the menu lcated in the tl bar, select the File Imprt ptin. 2. A windw will pp-up with several imprting ptins, select General Existing Prjects int Wrkspace. 3. Select Brwse in the dialg windw and search fr the lcal cpy f where the ADuCM360-IDE examples are. If yu used the default directry that can be fund here: C:\Analg Devices\ADuCM360-IDE\Examples
4. Make sure that the check-bx Cpy prjects int wrkspace is checked (this creates a lcal cpy f the prjects and preserves the riginal versins) and press Finish. If yu imprted the example prgrams frm the installer, yu can skip ahead t Building the.elf/.hex Files sectin. The nly time yu will need t imprt frm the GIT repsitry, is if yu want t lk fr newly released/updated prgrams.
Hw t Imprt Existing Prjects frm the GIT Repsitry 1. Open the GIT perspective windw by navigating the menu near the tl bar. File Perspective Open Perspective Other GITand the press OK.
2. Clne the Git repsitry which cntains all the latest cde and prjects assciated with the ADuCM360. Ppulate the URI field with the fllwing address. 1. URI: - https://github.cm/analgdevicesinc/eval- ADICUP360.git
2. Click Next Next Finish
3. In the Git Repsitries windw, Right Click n Prjects flder and select the Imprt ptin. 4. Select the radi buttn fr Imprt existing Eclipse prjects and click n the prjects flder as the destinatin.
5. Click Next Finish Building the.elf/.hex Files
It's imprtant t build yur prject befre setting up the debug cnfiguratin. This will allw the debug cnfiguratin t autmatically ppulate the apprpriate fields. 1. Starting n the C/C+ + perspective, select the prject yu want t debug in the Prjects Explrer Windw. 2. Right click n the prject and select the Build Prject ptin. Culd als g up t the tl bar and click n the Hammer icn. Setting up a Debug Cnfiguratin fr the Prject A new debug cnfiguratin must be set up fr EACH applicatin yu intend n develping/debugging. S yu will have many different debug cnfiguratins, depending n the number f prgrams yu create/debug. 1. G t the menu bar and fllw this path, Run Debug Cnfiguratins Alternatively, lcate the small bug icn in the tl bar and click the small dwnward facing arrw t the right, and select the Debug Cnfiguratins ptin frm the menu.
2. Duble click the GDB OpenOCD Debugging cnfiguratin frm windw.
3. The necessary input fields shuld be ppulated, assuming that yu built yur prject in the previus step. The fllwing images shuld be used as a reference if sme f the fields are blank.
4. Next, switch t the Debugger tab and ensure the fllwing required GDB cmmands are present. 5. Finally, click the checkbx in the Cmmn tab --> Display in Favrites Menu t make the created debug cnfiguratin appearing in the Debug Cnfiguratins sectin f the menu:
Click Apply, then Clse. Debugging an Applicatin 1. Make sure the EVAL-ADICUP360 bard is cnnected t the cmputer via the DEBUG USB prt. (The micr USB cnnectr clsest t the DC barrel jack) 2. Using the tl bar, navigate t the small Debug icn and click n the dwnward arrw t the right. Select the debug
cnfiguratin yu want t dwnlad t the ADuCM360. 3. If this is the first time yu have launched OpenOCD, a pp-up windw will display asking fr access. Click n Allw Access.
4. If everything ges fine, in the Cnsle windw, yu will see a reprt withut errrs. As a reference, the full text shuld be similar t: Open On-Chip Debugger 0.10.0-dev-00025- g81cc011-dirty (2015-08-17-13:23) Licensed under GNU GPL v2
Fr bug reprts, read http://pencd.rg/dc/dxygen/bugs.html Inf : nly ne transprt ptin; autselect 'swd' adapter speed: 5000 khz adapter_nsrst_delay: 100 crtex_m reset_cnfig vectreset init_aducm Started by GNU ARM Eclipse Inf : CMSIS-DAP: SWD Supprted Inf : CMSIS-DAP: Interface Initialised (SWD) Inf : CMSIS-DAP: FW Versin = 1.0 Inf : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 ntrst = 0 nreset = 1 Inf : CMSIS-DAP: Interface ready Inf : clck speed 5000 khz Inf : SWD IDCODE 0x2ba01477 Inf : aducm360.cpu: hardware has 6 breakpints, 4 watchpints Inf : accepting 'gdb' cnnectin n tcp/3333 The relevant EEPROM sectrs f ADuCM360 are erased and the micrcntrller is prgrammed. Yu can fllw the prgress in the Cnsle windw. As an
apprximate reference yu will see smething similar t: target state: halted target halted due t debug-request, current mde: Thread xpsr: 0x81000000 pc: 0x00000a94 msp: 0x20001fe0 semihsting is enabled RESET: ADI halt after btkernel breakpint set at 0x000001f5 Warn : Only resetting the Crtex-M cre, use a reset-init event handler t reset any peripherals r cnfigure hardware srst supprt. target state: halted target halted due t debug-request, current mde: Thread xpsr: 0x01000000 pc: 0x000001f4 msp: 0x20002000, semihsting flash 'aducm360' fund at 0x00000000 Inf : Padding image sectin 0 with 3 bytes RESET: ADI halt after btkernel breakpint set at 0x000001f5 Warn : Only resetting the Crtex-M cre, use a reset-init event handler t reset any peripherals r cnfigure hardware srst supprt.
target state: halted target halted due t debug-request, current mde: Thread xpsr: 0x01000000 pc: 0x000001f4 msp: 0x20002000, semihsting RESET: ADI halt after btkernel breakpint set at 0x000001f5 Warn : Only resetting the Crtex-M cre, use a reset-init event handler t reset any peripherals r cnfigure hardware srst supprt. target state: halted target halted due t debug-request, current mde: Thread xpsr: 0x01000000 pc: 0x000001f4 msp: 0x20002000, semihsting ===== arm v7m registers (0) r0 (/32): 0x40002800 (1) r1 (/32): 0x00000001 (2) r2 (/32): 0x00000064 (3) r3 (/32): 0x00000000 (4) r4 (/32): 0x00000000 (5) r5 (/32): 0x00000000 (6) r6 (/32): 0x00000000 (7) r7 (/32): 0x00000000 (8) r8 (/32): 0x00000000
(9) r9 (/32): 0x00000000 (10) r10 (/32): 0x00000000 (11) r11 (/32): 0x00000000 (12) r12 (/32): 0x00000000 (13) sp (/32): 0x20002000 (14) lr (/32): 0xFFFFFFFF (15) pc (/32): 0x000001F4 (16) xpsr (/32): 0x01000000 (17) msp (/32): 0x20002000 (18) psp (/32): 0x6A850410 (19) primask (/1): 0x00 (20) basepri (/8): 0x00 (21) faultmask (/1): 0x00 (22) cntrl (/2): 0x00 ===== Crtex-M DWT registers (23) dwt_ctrl (/32) (24) dwt_cyccnt (/32) (25) dwt_0_cmp (/32) (26) dwt_0_mask (/4) (27) dwt_0_functin (/32) (28) dwt_1_cmp (/32) (29) dwt_1_mask (/4) (30) dwt_1_functin (/32)
(31) dwt_2_cmp (/32) (32) dwt_2_mask (/4) (33) dwt_2_functin (/32) (34) dwt_3_cmp (/32) (35) dwt_3_mask (/4) (36) dwt_3_functin (/32) 5. The user applicatin executin is then stpped autmatically at the first breakpint at the beginning f main() lp. Frm this pint n, yu can use the debug functins and features f the Eclipse envirnment. (Such as stepping thrugh,
breakpints, register reads, variable values, etc.) 6. When finished, the debugger has t be stpped. Click n red Stp buttn up in the tl bar, then right click n the debug applicatin in the Debug windw, and select the Terminate
and Remve ptin. Creating a New Prject The custmized Eclipse IDE that yu installed fr EVAL-ADICUP360 ffer the pssibility t create 2 types f prjects: Empty Prject and Hell Wrld Prject. Bth C and C++ frmats.
The idea f these templates is t have at the end a functinal ADuCM360 prject which can be run n the target. The basic system cnfiguratin is the same fr bth: - startup cde - memry map and linker script - system clck cnfiguratin - disabling watchdg - enabling clcks fr all peripherals - lw drivers libraries fr ADuCM360 micrcntrller The differences are regarding the cmplexity f the main() functin: the Empty template prvide an empty main() functin, being in this way a gd chse when yu want t start yur ADuCM360 prject frm the scratch; the Hell Wrld template is fr mre cmplex prjects. It prvide 1 sec time base and different pssibilities t display an utput message t the user. See belw hw t create the C prjects fr EVAL-ADICUP360 bard. The same steps being available fr C++ prjects as well. 1. T create a new prject, g t the menu bar and find File New C
Prject. 2. Prvide a name fr yur prject, and then chse Prject Type: Executable ADuCM36x C/C+ + Prject, with
the Tlchains: Crss ARM GCC. Press Next.
3. Chse as Prcessr cre: ADuCM360.
4. Select which type f prject d yu want: Cntent: Empty (add yur wn cntent) r Hell Wrld (with 1s timer).
5. The Use system calls and Trace utput ptins are available fr Hell Wrld template nly. 6. Yu can select varius settings fr yur prject (which can be changed later, in the prject settings, r as different pre-
prcessr definitins).
7. Select bth the cnfiguratin check bxes yu want t deply n.
8. On the next page select the cmpiler tlchain. It shuld will autmatically selected, just check r enter the right path t it. 9. Finally, press Finish and the prject will be created and yu can begin prgramming. Optins available fr "Hell Wrld" template nly
Use system calls available ptins are (see GNU ARM Eclipse supprt page): Freestanding - a typical embedded cnfiguratin, that des nt use the POSIX system calls (pen, clse, read, write, etc). POSIX (retargetting) - a mre elabrate embedded cnfiguratin where the applicatin makes use f these calls, but redirects the file descriptrs t lcal devices r files, by prviding custm implementatins fr the system calls (like _pen, _clse, _read, _write etc). This cnfiguratin allws t prt POSIX prgrams easier. Semihsting - a special testing cnfiguratin, that bridges all system calls t the hst perating system where the GDB server runs. This cnfiguratins is particularly interesting fr running test prgrams that can leave the test results in a file stred n the hst, fr autmated integratin in a test suite. Trace utput available ptins are: Nne (n trace utput) - a basic cnfiguratin that desn't use trace utput messages. ARM ITM (via SWO) - a specific cnfiguratin that help t print infrmatin via SWO pin when using J-Link.
Semihsting STDOUT stream - a mre cmplex cnfiguratin that cnfigure stdut t use a physical serial cnnectin as UART r any ther peripherals that ffer the pssibility t utput messages. Semihsting DEBUG channel - a debug specific cnfiguratin which enable semihsting in DEBUG mde and ffer the pssibility t use resurces frm the develpment platfrm n the embedded target via debugger. This can help the user t send trace stream t debugger cnsle (like trace_printf, trace_puts etc). Assign Device t the Prject using Packs This step will allw yu t access the ADuCM360 registers in debugger mde. In rder t see the device list it is required t have Packs plug-ins installed. This is already dne by the installer, hwever yu d need t update the Packs list, and then install a particular family f devices. 1. T update yur Packs library, g t the menu and Chse Windw Perspective Open Perspective Other 2. Click n Packs. Once pen, find the Packs windw, and click n the Update arrw in the upper-righthand crner.
3. After updating has cmpleted, find the flder fr Analg Devices and navigate dwn t the latest versin f ADuCM36x and right click and hit Install. T assign device t yur prject: - Select yur prject in the Prject explrer view - G t Prject tab frm Eclipse menu and select Prperties - G t C/C+ + Build Settings
- Select the desired cnfiguratin - Click n Device tab and expand the Analg Devices nde - Select ADuCM360 as a device and press OK