Differences

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

--- resources:eval:user-guides:eval-adicup3029:reference_designs:demo_adt7420 [24 May 2017 04:40] – created 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: @@
-====== Demo Title ======
+====== 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-PMDZ** shield, created using the Analog Devices Cross Core Embedded Studio.
-FIXME!  - You need to fix the header here, the page names itself after this heading.
-ADT7420 Temperature sensor Demo
 ===== General Description/Overview =====
-FIXME!  -  Add text, picture, images, that describe what you are doing.  Focus on the application, sensor types, end goal, any important themes or theories, equations or other important tables/information.  The more info here the better.
+The **ADICUP3029_ADT7420** project uses [[adi>en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/EVAL-ADT7420-PMDZ.html/ | EVAL-ADT7420-PMDZ]] PMOD which is a 16-bit ambient temperature sensor. It requires no calibration.
+===== Demo Video =====
+{{analogTV>5554821977001}}
+===== 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 =====
+  - Plug the **EVAL-ADT7420-PMDZ** PMOD into the **EVAL-ADICUP3029** board's I2C PMOD connector**(P9)**.
+  - 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.
-FIXME!  -  Add text, picture, images, that describe how to setup the example application hardware.  A list of boards, sensors, equipment, cables, etc needed to recreate the demo.  Step by step picture here are helpful with block diagrams on how to connect things, how to setup options on the boards (Like what UART switch position is the ADICUP3029 in?  What power switch position?  Is there a chip select jumper on the add-on board that needs to be set?)
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:adicup3029_adt7420.jpg?650|}}
 ===== Configuring the Software =====
-FIXME!  -  Add text, picture, images, code blocks that describe how to configure the software.  Things like changing the accelerometer range from 2g to 4g should be a trivial change for the customer.  We don't have to show them everything, but think of the application, and what parameters are most likely need to be customized by the user.  (like providing a an ID or password for a local gateway using WI-FI)
+In the //adt7420_app.h// header files you can configure the following parameters:
+\\
+    * **ADI_APP_DISPATCH_TIMEOUT** - //DISPATCH TIMEOUT// will define how often the data is sent over Bluetooth.
+    * **ADI_APP_USE_BLUETOOTH ** - //ENABLE BLUETOOTH// parameter - will either use Bluetooth or will have the option to print to console window in debug mode or terminal in release mode.
 ===== Outputting Data =====
-FIXME!  -  Add text, picture, images, that describe how to output data from the setup/application.  Is this a UART output, then show the customer a putty serial terminal with the correct baud rate and commands that need to be entered to get data.  Are there any calibrations that need to happen?  Show/explain how customers can run the calibration steps.  If this is a wireless demo, how do you get the information after it is sent to the cloud?  We can use our apps and tools, but the customer should be able to recreate this demo using the same tools/plugins/components you used to view the data.
+Once the hardware is setup and software is configured, user needs to select how they want to view the data coming from the temperature sensor(ADT7420).
-===== Obtaining the Source Code =====
+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
-We recommend not opening the project directly, but rather import it into CrossCore Embedded Studios and make a local copy in your workspace.
+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.
+{{ :resources:eval:user-guides:eval-adicup3029:reference_designs:adt7420_demo_launch_configurations.png?200|}}
+\\
+\\
-The source code and include files of the FIXME!**file_name_of_demo** can be found here:
+^ 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 |
+\\
+\\
+\\
-<WRAP round 80% download>
+==== Debug Launch Mode ====
-FIXME!  -  This will be either a link to a Git repository or a pack file somewhere, but make sure this is accessible to the customer.  We want them to take our code and use it because that means they are going to use our hardware, and we get paid when that happens.
+**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.
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:ad7420_debug_outputble.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:adt7420_adv.png?400 |}}
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:screenshot_2017-05-28-15-43-32.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.
+==== 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.
+    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:adt7420_release_outputble.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:adt7420_adv.png?400 |}}
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:screenshot_2017-05-28-15-43-32.png?300|}}
+\\
+===== Obtaining the Software =====
+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.  This is the EASIEST way to get started with the reference design.
+Importing the project into CrossCore is going to allow you to change parameters and customize the software to fit your needs, but will be a bit more advanced and will require you to download the CrossCore toolchain. Below screen shot shows how to open project from CCES Example browser.
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:adt7420_example_selection.png?920|}}
+The software for the **ADuCM3029_demo_adt7420** demo can be found here:
+<WRAP round 80% download>
+Prebuilt ADT7420 Hex File
+  * [[https://github.com/analogdevicesinc/EVAL-ADICUP3029/releases/download/Latest/ADuCM3029_demo_adt7420.hex| AduCM3029_demo_adt7420.Hex]]
+Complete ADT7420 Source Files
+  * [[https://github.com/analogdevicesinc/EVAL-ADICUP3029/tree/master/projects/ADuCM3029_demo_adt7420| AduCM3029_demo_adt7420 Source Code]]
-[[https://github.com/analogdevicesinc/EVAL-ADICUP360/tree/master/projects/ADuCM360_demo_cn0398| AduCM360_demo_cn0398 at Github]]
 </WRAP>
@@ Line 49: / Line 159: @@
 ==== Project Structure ====
-FIXME!  -  Add text, picture, images, that describe the project structure.  Any software flow diagrams or decision trees can be added her to help customers understand how the applications are structures.
+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; port configuration for I2C read/write; configuring and reading from ADT7420, UART read/write functions;
+{{:resources:eval:user-guides:eval-adicup3029:reference_designs:ad7420_project_directory.png?650|}}
+\\
+adt7420_app.cpp and adt7420_app.h are the main source and header files related to **ADICUP3029_ADT7420** be found under RTE/ADuCM3029 folder.ADT7420 sensor software drivers are located in RTE/Sensor folder. All ADuCM3029 related drivers can BLE related files can be seen under RTE/Board_Support folder.
+\\
+**pinmux.c** – contains GPIO pinmuxing for UART and SPI.
+\\
+\\
+====== More Information ======
+{{page>resources:eval:user-guides:eval-adicup3029:reference_designs:ble_packet}}
 // End of Document //

Wiki

Analog Devices Wiki

Differences

Analog Devices Wiki

Differences

Page Tools