Wiki

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
resources:eval:user-guides:eval-adicup3029:reference_designs:demo_pmodacl2 [29 Jun 2017 18:14]
lgarber [Release Mode]
resources:eval:user-guides:eval-adicup3029:reference_designs:demo_pmodacl2 [19 Jul 2017 22:26] (current)
Brandon more specific directions
Line 7: Line 7:
 ===== General Description/​Overview ===== ===== General Description/​Overview =====
  
-The **ADICUP3029_ADXL362** project uses [[http://​store.digilentinc.com/​pmod-acl2-3-axis-mems-accelerometer/​ | PmodACL2 ​shield]] which is a 3-axis MEMS accelerometer powered by ADXL362.The accelerometer is interfaced via SPI protocol and users may receive up to 12-bits of resolution for each axis of acceleration. ADXL362 supports freefall detection as well as motion activated sleep and wakeup modes.+The **ADICUP3029_ADXL362** project uses [[http://​store.digilentinc.com/​pmod-acl2-3-axis-mems-accelerometer/​ | PmodACL2 ​PMOD]] which is a 3-axis MEMS accelerometer powered by ADXL362. ​ The accelerometer is interfaced via SPI protocol and users may receive up to 12-bits of resolution for each axis of acceleration. ADXL362 supports freefall detection as well as motion activated sleep and wakeup modes.
  
 ===== Demo Requirements ​ ===== ===== Demo Requirements ​ =====
Line 28: Line 28:
  
 ===== Setting up the Hardware ===== ===== Setting up the Hardware =====
-Plug the **Pmod ACL2** ​shield ​into the **EVAL-ADICUP3029** board'​s SPI1 PMOD connector ​as shown in the below picture.The ​**ADICUP3029_ADXL362** use **UART** connection via **P0.10/P0.11** of **[[http://​www.analog.com/​en/​products/​processors-dsp/​microcontrollers/​precision-microcontrollers/​aducm3029.html | ADuCM3029]]** to communicate with PC terminal. Make sure S2 switch is towards ​**USB**. **SPI** communication via SPI1 between ​ADICUP3029 and PmodACL2.+  - Plug the **Pmod ACL2** ​PMOD into the **EVAL-ADICUP3029** board'​s SPI1 PMOD connector ​(P8) 
 +  - Place the **(S5)** switch position to read "Wall/USB", and the **(S2)** switch position to read "​USB"​. 
 +  ​Plug in the micro USB cable into the **(P10)** USB port on the EVAL-ADICUP3029and the other end into the PC or laptop.
  
 {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adicup3029_pmodacl2.jpg?​650|}} {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adicup3029_pmodacl2.jpg?​650|}}
- 
  
 ===== Configuring the Software ===== ===== Configuring the Software =====
Line 42: Line 43:
 ===== Outputting Data ===== ===== Outputting Data =====
  
-Once the hardware and software is configured, user needs to follow on screen instructions ​to run ADXL362 ​accelerometer ​demo.+Once the hardware ​is setup and software is configured, user needs to select how they want to view the data coming from the accelerometer ​sensor(ADXL362).
  
-Following ​is the UART configuration+There are **three** different ways to visualize the data: 
-    ​Select COM Port +  * CrossCore Embedded Studio Console Window (through semihosting) 
-    Baud rate9600 +  * Serial Terminal Program (such as Putty or Tera Term) 
-    Data: 8 bit +  * IoTNode Smart Device App 
-    ​Parity:​ none + 
-    Stop: 1 bit +Depending on how you want to operate the board and visualize the data, there are two different options that must be selected from.  Below is a table outlining ​the general operation, and you need to click on which **launch** file you need to program onto the EVAL-ADICUP3029,​ and hit the **<​F5>​** key on your keyboard
-    Flow Control: none +{{ :resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adt7420_demo_launch_configurations.png?​200|}} 
-\\+\\  
 +\\  
 + 
 +Data Output Destination ^ Connected to Debugger ^ Configuration File ^ 
 +^ CCES Console Window | Yes | ADICUP3029_Debug.launch | 
 +^ PC/Laptop Serial Terminal | No | ADICUP3029_Release.launch | 
 +^ IoTNode Smart App | Yes | ADICUP3029_Debug.launch | 
 +^ IoTNode Smart App | No | ADICUP3029_Release.launch | 
 +\\  
 +\\  
 +\\ 
    
 ==== Debug Mode ==== ==== Debug Mode ====
-In debug build based on ADI_APP_USE_BLUETOOTH macro value the application either sends sensor values ​to the console + 
-or to the android applicationBelow screenshots depict different scenarios.+**Debug launch mode** is used when connected to the debugger.  ​In debug mode, all the outputs are directed ​to the console ​window of the CrossCore tools via semihosting The data is also sent by default to the IoTNode smart app (ADI_APP_USE_BLUETOOTH =1), but can be turned of if desired by setting ADI_APP_USE_BLUETOOTH = 0
 \\ \\
-Figure shows when ADI_APP_USE_BLUETOOTH is set to 1, sensor data is sent to android application. 
  
 +Figure shows when ADI_APP_USE_BLUETOOTH is set to 1, sensor data is sent to android application.
  
 {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_debug_ouputble.png?​920|}} {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_debug_ouputble.png?​920|}}
  
-Figure ​shows the output on android device+If you have the app installed on your phone, these figure ​shows the output on android device
 +<WRAP center round important 80%> 
 +Do not try to connect directly (or pair) to the EVAL-ADICUP3029 from your phone. ​  
 +  - Simply open up the IoTNode application on your phone. 
 +  - "​Scan"​ for nearby demos. ​  
 +  - Once you find your demo, click on it to open it up. 
 +</​WRAP>​
  
-{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_dev.png?​700|}} +\\  
-\\ +{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_dev.png?​600 |}} 
-{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_screen2.png?​400|}} +{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_screen2.png?​300|}} 
-\\+\\  
 + 
 +It's important to remember that when you use the Debug.launch file that you hit the "​play"​ button when using the tools or else your program will not run.
  
 Figure shows when ADI_APP_USE_BLUETOOTH is set to 0, Sensor data is printed on to console. Figure shows when ADI_APP_USE_BLUETOOTH is set to 0, Sensor data is printed on to console.
Line 74: Line 93:
  
 ==== Release Mode ==== ==== Release Mode ====
-Release mode is used for running without the debugger. When in release mode, console output is redirected to UART. If Bluetooth is enabled sensor data is sent to android application. If disabled sensor data is redirected to UART. Below screenshots show different scenarios. 
  
-Figure shows when ADI_APP_USE_BLUETOOTH is set to 0+**Release launch mode** is used for running without the debugger connected. When in release mode, console output is redirected to UART.  Bluetooth is enabled, and sensor data is sent to android application. If disabled, sensor data is directed only to the UART. If you are using the UART to make print to the PC/laptop, here are the settings your TCP client must be set too. 
 +Following is the UART configuration. 
 +    Select COM Port 
 +    Baud rate: 9600 
 +    Data: 8 bit 
 +    Parity: none 
 +    Stop: 1 bit 
 +    Flow Control: none 
 +\\  
 + 
 +Figure shows when ADI_APP_USE_BLUETOOTH is set to 1
  
 {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adx362_reease_output.png?​920|}} {{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adx362_reease_output.png?​920|}}
 +
 +If you have the app installed on your phone, these figure shows the output on android device.
 +<WRAP center round important 80%>
 +Do not try to connect directly (or pair) to the EVAL-ADICUP3029 from your phone.  ​
 +  - Simply open up the IoTNode application on your phone.
 +  - "​Scan"​ for nearby demos.  ​
 +  - Once you find your demo, click on it to open it up.
 +</​WRAP>​
 +\\ 
 +\\ 
 +{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_dev.png?​600 |}}
 +{{:​resources:​eval:​user-guides:​eval-adicup3029:​reference_designs:​adxl362_screen2.png?​300|}}
 +\\ 
  
 ===== Obtaining the Source Code ===== ===== Obtaining the Source Code =====
resources/eval/user-guides/eval-adicup3029/reference_designs/demo_pmodacl2.txt · Last modified: 19 Jul 2017 22:26 by Brandon