VBB-SHIELD-Q84¶

VBB Avatar Q84 with Arduino Shield footprint.

Breadboard Footprint¶

Schematic Symbol¶

Not available > Roadmap: Bind schematic.

Description¶

The VBB-SHIELD-Q84 is an PIC18F47Q84 with VBB Avatar firmware interface chip with an Arduino Shield footprint.

PinOut¶

Pin	Name	Description
1	0->RX(In)	Digital 0 and Hardware UART RX pin
2	1<-TX(In)	Digital 1 and Hardware UART TX pin
3	2	Digital 2
4	3~	Digital 3 with PWM output
5	4	Digital 4
6	5~	Digital 5 with PWM output
7	6~	Digital 6 with PWM output
8	7	Digital 7
9	8	Digital 8
10	9~	Digital 9 with PWM output
11	10	Digital 10 with PWM output
12	11	Digital 11 with PWM output
13	12	Digital 12
14	13	Digital 13
15	A0	Analog 0
16	A1	Analog 1
17	A2	Analog 2
18	A3	Analog 3
19	A4	Analog 4
20	A5	Analog 5

SPICE¶

Yes. Mixed Mode.

OpenVBB¶

Yes.

Properties¶

Property	Values	Description
HEX App	–	Optional HEX to program on launch
Connection	COM \| EDGE	The serial port to connect to the Arduino Host
Serial Baud	9600	The baud of the Arduino serial passthrough
Host	Generic \| Device*	The baud of the Arduino serial passthrough

HEX App¶

The HEX App is an optional binary HEX file as produced by the Arduino IDE or other AVR compiler. Using this property allows firmware for the virtual hardware to be saved with the project. On runtime startup the HEX file is programmed into the host device as selected by the HOST property using the VBB-Avatar-Q84 chip as an ISP Programmer. Note : If the HEX does not include a bootloader the device will need to be programmed with a HEX containing a bootloader before being able to be programmable again with the Arduino IDE. When programming the host device using the bootloader using the Arduino IDE or other development tool leave the HEX App property empty.

Property Dialog¶

To attach a HEX directly drag-and-drop the HEX onto the Avatar in the Breadboard. Use the property dialog to:

Use a file picker to locate the HEX
Clear the HEX property

TIP: How to create a HEX¶

When using the Arduino IDE use the following commands to create and locate the HEX file on your computer

Sketch Menu => Export compiled Binary ( Ctrl + Alt + S )

Sketch Menu => Show Sketch Folder ( Ctrl + K )

Connection¶

The Avatar connection is slected by drop-dropdown

There are two type of connection. A direct COM serial connection or a remote EDGE connection.

COM¶

The COM port which is attached to a real Arduino UNO hosting a real VBBMicro-47K42A328P. This property dropdown list is populated by enumerating the supported devices list using the UWP generic USB driver. Windows Store App security requires that devices to be supported must be declared in the package using their USB VID:PID descriptors.

Currently Supported Arduino devices

Arduino UNO by Arduino.cc ( 2341:0043 )
Arduino UNO by Arduino.org ( 2A03 0043 )

Contact VirtualBreadboard support if you would like to request support for other compatible devices to be added to the next release.

>FTDI devices are not supported by the UWP generic device driver. Only USB emulated serial port firmware can be supported.

EDGE¶

When publishing your application using Remofity use the EDGE setting to enable the COM port to be late-bound to the serial port selected by the Browser or EDGE-App.

Host¶

There are many different boards that support the Arduino Shield form factor. The Host setting selects a specific device so it can be programmed using the ISP programmer when the HEX property is not empty.

Devices supported by the ISP programmer

Generic : no device - program using 3rd party tool
ATMega328P ( Arduino UNO and compatibles)
ATMega32U4 ( Arduino Leonardo and compatibles)
ATMega328 ( Arduino Duemilanov and compatibles)
ATMega168 ( Arduino Duemilanov and compatibles)

Serial Baud¶

Serial Baud is the communication speed that should be used when calling Serial.begin(baud) in the Arduino application. The Avatar will listen to the RX/TX pins and pass-through the serial it is wired up to a UART device in VBB.

Useage¶

Notes¶

Add deployment details to deploy to the real device