Anthony Huereca

Rev G Tower Board Changes

Discussion created by Anthony Huereca Employee on Apr 26, 2013

The information below is for archival purposes only for persons who had early Vybrid access. All Tower Boards at Market Launch (July 9th) are Rev G.

 

There were a couple of functional changes on the Rev G tower board as compared to previous board revisions. Users coming to Rev G from previous boards need to be aware of these changes.

 

 

 

The changes on Rev G were:

  • Uses 1.1 silicon instead of 1.0
  • The default serial port (UART1) is now connected to OpenSDA by default for use by serial-to-USB app. UART2 is now connected to TWR-SER by default. This is modifiable via jumpers J23 and J24 which were added on Rev G. The goal was to enable the A5 core to control one UART, while the M4 core controlled the other.
  • The default OpenSDA application is the serial-to-USB app, and is no longer the CMSIS-DAP app.

 

Common Issues:

I don't see any terminal output anymore

Most Vybrid software uses UART1 by default for terminal data, which on Rev G is routed only to the OpenSDA circuit by default. This is to avoid the requirement for an external hardware serial-to-USB convertor and a TWR-SER board.

 

There are three options to see serial data:

1) Connect to the virtual serial port enumerated by OpenSDA when the serial-to-USB app is installed (which is default app on Rev G). The drivers can be found on the MSD drive that that app enumerates.

2) Change software to use UART2, connected to TWR-SER by default, instead of UART1

3) Change jumpers J23 and J24 so that UART1 goes to the TWR-SER and UART2 goes to OpenSDA instead.

 

I cannot connect to the board in DS-5 anymore

Load the CMSIS-DAP app into the OpenSDA firmware.

Note that the CMSIS-DAP firmware *does not* provide serial-to-USB functionality and thus you must use the TWR-SER board for the serial port.


The colors are wrong on the TWR-LCD-RGB now

Due to fixing errata e6160 in 1.1, the data format for images in 16bpp changed. Some of the bare-metal examples used 16bpp data. The solution is to put the data in the proper RGB format. Various examples are being updated to do this.


The out of box demo described doesn't match what I see happening

The Out-of-Box demo referenced in the printed guide is not programmed on some SD cards. It is just a preliminary version that boots Linux. Rev G boards at launch will have the correct code on the SD card and will match up with the printed QSG.

Outcomes