Rev D1 - Initial Boot

[kb1lqd]

Booting of the first REV D1 PCBA from PCB:NG. This board has no through hole components, GPS, or SMA antenna connector until it is soldered at a later time. This ticket is to capture the boot process.

Initial Steps Needed

• Plug into USB and verify proper USB recognition
• Determine USB virtual COM port
• Update FTDI IC
• Update hardware allocations for GPIO pins to proper revision updates
• Build firmware .TITXT HEX file for bootloading
• Program with bootloader
• verify non-RF portions of the hardware

h1. Unboxed PCBA

This PCBA was unboxed and has not had any manually installed parts placed.

h1. USB Connection

• Plugged into USB (COM 5)
• Note, FTDI reprogramming will cause this COM port to change

h1. Update FTDI IC

• Update CBUS operations to GPIO for bootloader operations

• Update to high power mode 500mA.

h1. USB Connection #2

• Plugged into USB (COM 7)

h1. Firmware Build and Bootloader

I created a branch in firmware from master for the initial boot (https://github.com/FaradayRF/Faraday-Firmware/tree/REV-D1-Initial-Boot).

h2. Create TI HEX Firmware File

Right-click the project and navigate to and enable the TI HEX Utility. The enabled the ti-txt output option

Simply compiling the program will now output a TXT file. I created Faraday_REVD1_Bringup.txt

Copy this file into the bootloader folder and edit the filename in the Auto_Upload.py to match that of the next .txt file created. Edit the CreateBslScript() function line in Create_TI-TXT_Parse.py to match the COM port being used by the device to be programmed.

textfile.writelines(('MODE 6xx UART 9600 COM7 PARITY', '\n'))

Run the Auto_Upload.py file to create a new FaradayFirmwareUpgradeScript.txt` which contains the bootstrap loader scripting language output. The programming will automatically start!

In the act of programming:

h1. Verify Booting and Basic Operations

h2. See UART Telemetry

Verified proper initial boot of "NOCALL" is being sent over UART! This is the initial factory default settings if no programmed state exists.

h2. Tutorial 1-1 Proxy Basics

I decoded data from the unit!

h2. Tutorial 1-3 Device Configuration

I'm reprogramming the unit from the default NOCALL to KB1LQD-5.

For some reason I keep getting this error, looks like a proxy/device programming script error?

h2. Tutorial 1-4 LED Toggling

Yep, the GREEN LED toggled as intended and UART echo'd back a message!