Loading VTOS firmware images using U-Boot
This application note describes how to load VTOS firmware images for the T2xxx processor family into DDR using U-Boot.
Loading the firmware image
- Connect a serial cable between the UART1 interface of the T2xxx processor on your board and your host PC.
- Open a terminal emulator, such as TeraTerm, setting the serial port settings to 115200 baud, 8 data bits, no parity, 1 stop bit, and no flow control.
- Power on your board and interrupt the U-Boot autoboot sequence by pressing any key in the terminal window.
- At the U-Boot prompt, transfer the VTOS firmware binary into memory by typing this command:
- U-Boot will indicate that it is ready to receive the file once it starts printing “C” characters to the screen.
- Start a YMODEM file transfer. Using TeraTerm, select File->Transfer->YMODEM->Send…
- Type the following into the File name: field: %KOZIO_HOME_3%\VTOS_Scan\fw\vtos.qoriq_t2_scan_ethernet.uart1_clkin_66.bin
- While TeraTerm transfers the file, the progress dialog looks like this:
- At the completion of the file transfer, U-Boot displays the number of bytes transferred and re-displays the command prompt.
- To boot up the VTOS Scan Ethernet image, type this command at the U-Boot prompt:
- The terminal output should show the VTOS firmware boot message.
- Disconnect TeraTerm from the serial port. You can either exit TeraTerm, or select File->Disconnect.
Configuring the serial connection under VTOS Developer
After loading the firmware image using U-Boot, VTOS Developer to create a new fixture connection and connect to your board.
- Under the Project->Connection Settings, right-click Add Fixture.
- For the newly created fixture, set the Connection Type to Serial (COM). Leave the Target Loader and Target UART fields blank. Set the COM Port field to the serial port connected to your board. The example below shows a board connected using COM1.
- Save your project: File->Save Project.
- Ensure the VTOS Scan Ethernet task is active, and click connect. The console output should show firmware information as shown below:
- Create and run tests normally – there is no change to the operation of tests whether you use a Codewarrior TAP or a serial port for communication.