This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:eval:user-guides:eval-adicup3029:reference_designs:demo_adt7420 [28 May 2017 23:44] – Srinivas Gollakota | resources:eval:user-guides:eval-adicup3029:reference_designs:demo_adt7420 [14 Mar 2021 06:04] (current) – [Obtaining the Source Code] adding in .Hex files Zuedmar Arceo | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== ADT7420 Temperature Sensor Demo [with EVAL-ADT7420_PWDZ]====== | + | ====== ADT7420 Temperature Sensor Demo [with EVAL-ADT7420-PMDZ]====== |
- | The **ADICUP3029_ADT7420** is a temperature sensor demo project for the **EVAL-ADICUP3029** base board with additional **EVAL-ADT7420_PWDZ** shield, created using the Analog Devices Cross Core Embedded Studio. | + | The **ADICUP3029_ADT7420** is a temperature sensor demo project for the **EVAL-ADICUP3029** base board with additional **EVAL-ADT7420-PMDZ** shield, created using the Analog Devices Cross Core Embedded Studio. |
===== General Description/ | ===== General Description/ | ||
- | The **ADICUP3029_ADT7420** project uses [[http:// | + | The **ADICUP3029_ADT7420** project uses [[adi>en/ |
+ | |||
+ | ===== Demo Video ===== | ||
+ | |||
+ | {{analogTV> | ||
+ | |||
+ | ===== Demo Requirements | ||
+ | |||
+ | The following is a list of items needed in order to replicate this demo. | ||
+ | * Hardware | ||
+ | * EVAL-ADICUP3029 | ||
+ | * EVAL-ADT7420-PMDZ | ||
+ | * Mirco USB to USB cable | ||
+ | * PC or Laptop with a USB port | ||
+ | * Software | ||
+ | * ADICUP3029_ADT7420 software | ||
+ | * Inside Sensor_Sw Pack (1.0.0 or higher) | ||
+ | * CrossCore Embedded Studio (2.6.0 or higher) | ||
+ | * ADuCM302x DFP (2.0.0 or higher) | ||
+ | * ADICUP3029 BSP (1.0.0 or higher) | ||
+ | * Android IoTNode App (optional - For Bluetooth transmission only) | ||
+ | * Serial Terminal Program (Required for running in release mode only) | ||
+ | * Such as Putty or Tera Term | ||
===== Setting up the Hardware ===== | ===== Setting up the Hardware ===== | ||
- | Plug the **EVAL-ADT7420_PWDZ** shield | + | - Plug the **EVAL-ADT7420-PMDZ** PMOD into the **EVAL-ADICUP3029** board' |
+ | - 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-ADICUP3029, and the other end into the PC or laptop. | ||
{{: | {{: | ||
- | |||
===== Configuring the Software ===== | ===== Configuring the Software ===== | ||
Line 23: | Line 46: | ||
===== Outputting Data ===== | ===== Outputting Data ===== | ||
- | Once the hardware and software is configured, user needs to follow on screen instructions | + | Once the hardware |
+ | There are **three** different ways to visualize the data: | ||
+ | * CrossCore Embedded Studio Console Window (through semihosting) | ||
+ | * Serial Terminal Program (such as Putty or Tera Term) | ||
+ | * IoTNode Smart Device App | ||
+ | |||
+ | 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, | ||
+ | {{ : | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ^ 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 Launch Mode ==== | ||
+ | |||
+ | **Debug launch mode** is used when connected to the debugger. | ||
+ | \\ | ||
+ | |||
+ | Figure shows when ADI_APP_USE_BLUETOOTH is set to 1, sensor data is sent to android application. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | 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. | ||
+ | - " | ||
+ | - Once you find your demo, click on it to open it up. | ||
+ | </ | ||
+ | |||
+ | \\ | ||
+ | {{: | ||
+ | {{: | ||
+ | \\ | ||
+ | |||
+ | It's important to remember that when you use the Debug.launch file that you hit the " | ||
+ | |||
+ | ==== Release Launch Mode ==== | ||
+ | |||
+ | **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. | Following is the UART configuration. | ||
Select COM Port | Select COM Port | ||
Line 33: | Line 103: | ||
Flow Control: none | Flow Control: none | ||
\\ | \\ | ||
- | |||
- | ==== 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 application. Below screenshots depict different scenarios. | ||
- | \\ | ||
- | 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 |
+ | {{: | ||
- | Figure | + | If you have the app installed on your phone, these figure |
- | \\ | + | <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. |
- | {{: | + | - " |
+ | - Once you find your demo, click on it to open it up. | ||
+ | </ | ||
+ | \\ | ||
+ | {{: | ||
+ | {{: | ||
\\ | \\ | ||
- | ==== Release Mode ==== | + | ===== Obtaining the Software ===== |
- | 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 1 | + | There are two basic ways to program the ADICUP3029 with the software for the ADT7420. |
+ | - Dragging and Dropping the .Hex to the Daplink drive | ||
+ | - Building, Compiling, and Debugging using CCES | ||
- | {{: | + | Using the drag and drop method, the software is going to be a version that Analog Devices creates for testing and evaluation purposes. |
- | ===== Obtaining the Source Code ===== | + | Importing |
- | + | ||
- | We recommend not opening | + | |
Line 65: | Line 134: | ||
- | The source code and include files of the **ADICUP3029_ADT7420** demo can be found here: | + | The software for the **ADuCM3029_demo_adt7420** demo can be found here: |
<WRAP round 80% download> | <WRAP round 80% download> | ||
- | <fc #ff0000>**ADD GITHUB LINK HERE!**</fc> | + | Prebuilt ADT7420 Hex File |
+ | | ||
+ | Complete ADT7420 Source Files | ||
+ | * [[https:// | ||
</ | </ | ||
Line 88: | Line 161: | ||
The **ADICUP3029_ADT7420** is a C project that uses ADuCM3029 C/C++ Project structure. | The **ADICUP3029_ADT7420** is a C project that uses ADuCM3029 C/C++ Project structure. | ||
- | This project contains: system initialization part - disabling watchdog, setting system clock, enabling clock for peripherals; | + | This project contains: system initialization part - disabling watchdog, setting system clock, enabling clock for peripherals; |
{{: | {{: | ||
Line 98: | Line 171: | ||
\\ | \\ | ||
\\ | \\ | ||
+ | ====== More Information ====== | ||
+ | |||
+ | {{page> | ||
// End of Document // | // End of Document // | ||