Prepare to use the RoadRunner Jr:
Please go to the
RoadRunner web page for more
info. on USB driver installation and verification. Operating
instructions:
The circuitry of the RoadRunner-Jr.
module is very simple and you probably would know how to use it by
reading the schematics.
It provides a USB to TTL conversion for a serial communication. The
serial communication supports xon-xoff protocol and the handshaking
signals /RTS and /CTS are available on the module, but are not being
used.
Although its main application is to team up with our ThunderBird12 or
Dragonfly12 module to form a quick prototype platform, but it will also
work with other micro controller module as well.
The 5V voltage from a USB port is very convenient for testing program
code, but if you are going to test motor or other power devices, they
might cause a reset on a ThunderBird module if they draw too much
current and force the VCC drop below 4.5V. If that's the case you should
use a external AC adapter instead of getting power from USB or a
separate power supply unit for the power devices.
When it's plugged onto a solderless breadboard it can provide VCC and
ground buses for the breadboard.
It also provides VCC, ground and SCI communication signals for the
ThunderBird12 module or the Dragonfly12-Plus DIP module.
If it's used
with a ThunderBird12 module based on the MC9S12DG256:
1. Plug the RoadRunner Jr. onto a soldless breadboard.
2..Plug the ThunderBird12 module and align the pin 57 - pin 60 of the
ThunderBird12 module, pin to pin, to the J1 of the RoadRunner Jr..
When the ThunderBird12 module is pre-installed with bootloader and
D-Bug12 monitor, the states of the 2-position DIP switch (S2) are tested
by the bootloader for selecting one of 4 operating modes during power up
or reset, and the four LED indicators will blink one at a time from left
to right to indicate that the bootloader is functioning. Then one of
them will be lit to indicate the selected operating mode and other three
will be turned off. When you learn HCS12 / 9S12 programming with D-Bug12
monitor, you might need to change operating modes quite often, so a mode
indicator is helpful.
The 4 operating modes tested by the bootloader are EVB, Jump to EE, BDM
POD and Bootloader.
When the ThunderBird12 module is pre-installed with serial monitor, the
state of the left switch of the 2-position DIP switch (S2) is tested by
the serial monitor for selecting RUN or LOAD mode during power up or
reset, and the four LED indicators will blink one at a time from right
to left to indicate that the serial monitor is functioning. If the left
switch is placed in "LOAD" mode the monitor will wait for a command from
PC. If the left switch is placed in "RUN" mode the LEDs will sweep back
from left to right to indicate that the program execution is diverted to
the user code.
If the bootloader or the serial monitor is not installed or erased by a
BDM, the 4 LED indicators will not blink during power up or reset.
If it's used with a Dragonfly12-Plus module
based on the MC9S12C32 or
MC9s12C128, you need make 4 connections for the
Dragonfly12-Plus module: see the wiring in the picture at:
http://www.evbplus.com/Dragonfly12P_9s12/DIP40_9s12.html
1. Plug the RoadRunner-Jr. onto a soldless breadboard.
2. Connect the pin 1 of the Dragonfly12-Plus module to GND.
Connect the pin 2 of the Dragonfly12-Plus module to VCC.
Connect the pin 34 (PS0) of the Dragonfly12-Plus module to
the TX output of the RoadRunner-Jr. module.
Connect the pin 35 (PS1) of the Dragonfly12-Plus module to
the RX input of the RoadRunner-Jr. module.
The Dragonfly12-Plus module is pre-installed with serial monitor only,
because it does not have enough flash memory to hold the D-Bug12
monitor. The state of the slide switch (S2) is tested by the serial
monitor for selecting RUN or LOAD mode during power up or reset, and the
LED indicator will blink twice to indicate that the serial monitor is
functioning. If the slide switch is placed in "LOAD" mode the monitor
will wait for a command from PC. If the slide switch is placed in "RUN"
mode the LEDs will flash 2 more times to indicate that the program
execution is diverted to the user code.
|