Wiki

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
resources:tools-software:product-support-software:ad7124-stm32 [26 Jul 2019 18:51] – Adding source Michael Bradleyresources:tools-software:product-support-software:ad7124-stm32 [24 Jan 2020 10:48] (current) – Adopted AD7124 pin names for connection table Michael Bradley
Line 120: Line 120:
 <note important>The names of the port handles are defined by the Device Configuration Tool based on the selected processor and pin choices. If using a different processor or pins, these may need to be changed in the platform_drivers.c and platform_support.c files so they match up.</note> <note important>The names of the port handles are defined by the Device Configuration Tool based on the selected processor and pin choices. If using a different processor or pins, these may need to be changed in the platform_drivers.c and platform_support.c files so they match up.</note>
 === syscalls.c === === syscalls.c ===
-In the following function, the 'len' parameter was found to always be '1024' for the library and build environment used to develop the example code.+In the _read(...) function, the 'len' parameter passed in was found to always be '1024' for the library and build environment used to develop the example code.
 <code c> <code c>
 int _read(int file, char *ptr, int len) int _read(int file, char *ptr, int len)
 </code> </code>
-In order to support the use of getchar(), len was set to 1 before the for loop.  While this is sufficient for getchar() to work, it does not support use of other stdio.h functions such as scanf(...).+In order to support the use of getchar(), the expression 'len 1;' was added immediately before the for loop in the _read(...) function.  While this is sufficient for getchar() to work, it does not support use of other stdio.h functions such as scanf(...).
 ==== Adding AD7124 Example Files ==== ==== Adding AD7124 Example Files ====
 The distribution of the AD7124 source and header files can be added to the project that has been created.  The files can be added in a dedicated 'adi' directory, or in the main 'src' directory, or split as appropriate between 'src' and 'inc' directories, according to the file structure being used. If adding new source and header file locations, then these will need to be added to the build settings as necessary, in the relevant 'Include paths' in the MCU GCC Compiler configuration. The distribution of the AD7124 source and header files can be added to the project that has been created.  The files can be added in a dedicated 'adi' directory, or in the main 'src' directory, or split as appropriate between 'src' and 'inc' directories, according to the file structure being used. If adding new source and header file locations, then these will need to be added to the build settings as necessary, in the relevant 'Include paths' in the MCU GCC Compiler configuration.
Line 142: Line 142:
  
 ^ AD7124 SPI Signal ^ SDP Breakout Board ^ NUCLEO-L476     ^ ^ AD7124 SPI Signal ^ SDP Breakout Board ^ NUCLEO-L476     ^
-| GND   | 81  | GND on CN5.7      |+| GND  | 81  | GND on CN5.7      |
 | SCLK  | 82  | D3 (PB3) on CN9.4 | | SCLK  | 82  | D3 (PB3) on CN9.4 |
-MISO  | 83  | D5 (PB4) on CN9.6 | +DOUT/RDYB | 83  | D5 (PB4) on CN9.6 | 
-MOSI  | 84  | D4 (PB5) on CN9.5 | +DIN  | 84  | D4 (PB5) on CN9.5 | 
-| CSB   | 85  | D6 (PB10) on CN9.7|+| CSB | 85  | D6 (PB10) on CN9.7|
  
 ==== Analog Input ==== ==== Analog Input ====
resources/tools-software/product-support-software/ad7124-stm32.txt · Last modified: 24 Jan 2020 10:48 by Michael Bradley