If using TeraTerm, you should be able to keep the defaults, however adjustments may need to be made to how carriage return (CR) is handled in order for everything to display correctly. Set the baud-rate for 230400, configure the console terminal settings as shown in the picture above and select the connected controller board’s COM port. Here TeraTerm is used as an example, Analog Devices does not endorse any particular program for this, but TeraTerm works well and is made freely available, other terminals such as CoolTerm, or PuTTY will work.
#Coolterm code serial
It is necessary to connect a serial terminal-emulator to interact with the running firmware. Any terminal-emulator should work, but it is not possible for Analog Devices to test everyone. The firmware is delivered as a basic, text-based user-interface that operates through a UART on the controller board using the same USB cable that is used to flash the firmware to the boards. Unmodified, the code will communicate over any serial terminal emulator (CoolTerm, putty, etc) using the UART provided by the controller board over USB. The software described below allows for an Mbed enabled controller board to be connected with an Analog Devices evaluation board. This reduces the hardware dependency as any Mbed enabled board can be used with same firmware with little modifications (changing a pin mapping).
#Coolterm code driver
The Mbed Platform simplifies the overall software development process by providing the low-level driver support. This guide focuses on the SDP-K1, connected to the DC2873A-B or DC2904A-B board, but it should be general enough to cover any compatible controller board (the controller board should be Mbed-enabled, and expose at least SPI or I2C and some GPIO's). See here for instructions on setting up an account and using the Keil Studio. The devices from LTC2686/8 family use SPI communication interfaces respectively.Īt this time Analog Devices supports Mbed code development only on the Keil Studio Cloud.
#Coolterm code drivers
The platform drivers use mbed-os libraries to access low level peripheral (like GPIOs, SPI, I2C, etc). The bottom layer of Platform Drivers is responsible for Low Level Interface.
These APIs allows direct access to device register map in order to read/write device registers. The middle layer of No- OS device library has device specific APIs to interface with LTC2686/8 devices. The application layer uses the ADI Console Libraries to create console-based User Interactive (UI). The firmware example comprises 3 layers of software (from top to bottom): Console Application Layer, Device No- OS Layer and Platform Drivers (Mbed- OS) layer. This guide will focus interfacing the DC2873A-B or DC2904A-B evaluation board with Analog Devices SDP-K1 controller board or any an MBED-Enabled board. The LTC268X Mbed example software can be used as a starting point for developing your own code for Analog Devices DC2873A-B or DC2904A board in your own environment utilizing the benefits of the Mbed platform. The LTC2686/8 are 8/16-channel, 16-bit, ☑5 V digital-to-analog converters (DAC) with an integrated precision reference.
0 kommentar(er)
