Mail a friend
 Print this page
 Add to favorites


AT91eb01 - Atmel AT91EB01 Evaluation Board
cdb89712 - Crystal Semiconductor (Cirrus Logic) CDB89712 Evaluation Board
EBX7709 - Hitachi EBX7709 Board
evaluator7t - Samsung KS32C50100 on Evaluator7T Evaluation Board
MCB167 - MCB167-NET Evaluation Board
MBX860 - MBX860 Board
Net186 - AMD Net186 Board
RemotePC - PC
Segger - Schlumberger M16C Board

AT91EB01

Which compiler/tool are supported?

ARM Software Development Toolkit v2.50: ARM ASDT compiler (armcc v4.90) and ARM debugger (with Angel and Multi-ICE support). ADS compiler is also supported.
How do I download an executable file on the board with Angel?

Start ARM debugger (ADW). Goto Option/Configure Debugger. Select "remote_a" as target environment. Wait for the reset to complete.
Goto File/Load Image to load your image in the board.
How do I download an executable file on the board with Multi-ICE?

Install Multi-ICE from CDROM on your PC. Make sure your board has booted with Multi-ICE boot image.
Launch ARM Multi-ICE server and start ARM debugger (ADW). Goto Option/Configure Debugger. Select "Multi-ICE" as target environment. Wait for the reset to complete.

Goto File/Load Image to load your image in the board.
Anything special about the power supply?

Yes! Make sure to provide a 9V tension with the + (i.e. "plus") in the inside part of the connector.

cdb89712

Which compiler/tool are supported?

ARM Software Development Toolkit v2.50: ARM ASDT compiler (armcc v4.90) and ARM debugger (with Angel and Multi-ICE support). ADS and GHS compiler are also supported.
How do I download an executable file on the board with Angel?

Make sure your board has booted Angel.

Start ARM debugger (ADW). Goto Option/Configure Debugger. Select "remote_a" as target environment. Wait for the reset to complete.

Goto File/Load Image to load your image in the board.
How do I download an executable file on the board with Multi-ICE?


Install Multi-ICE from CDROM for CDB89712 Cirrus board. And copy the file 720.cfg from the CD into the ARM Multi-ICE directory (e.g. into ...\ARM\Multi-ICE\).

Make sure your board has booted with Multi-ICE boot image.

Launch ARM Multi-ICE server and select the 720.cfg in the menu "Load Configuration". Start ARM debugger (ADW). Goto Option/Configure Debugger. Select "Multi-ICE" as target environment. We experienced trouble on win98: the option "Setting/Port Setting/Force 4-bit" has to be selected. Wait for the reset to complete.

Goto File/Load Image to load your image in the board.

EBX7709

Which compiler/tool are supported?

SHC compiler. Debuger/load is Hitachi Debugging Interface (HDI).
These are software from Hitachi Micro System.
How do I download an .axe (executable) file on the board?

Launch HDI. Select the SH3 platform for the EBX7709.

evaluator7t

Which compiler/tool are supported?

ARM Software Development Toolkit v2.50: ARM ASDT compiler (armcc v4.90) and ARM debugger (with Angel and Multi-ICE support). ADS compiler is also supported.
How do I download an executable file on the board with Angel?

Make sure your board has booted Angel.

Start ARM debugger (ADW). Goto Option/Configure Debugger. Select "remote_a" as target environment. Wait for the reset to complete.

Goto File/Load Image to load your image in the board.
How do I download an executable file on the board with Multi-ICE?

Install Multi-ICE from CDROM on your PC. Make sure your board has booted with Multi-ICE boot image.

Launch ARM Multi-ICE server and start ARM debugger (ADW).
Goto Option/Configure Debugger. Select "Multi-ICE" as target environment.
Wait for the reset to complete.

Goto File/Load Image to load your image in the board.

MBX860

Which compiler/tool is supported?

DIABC Compiler. Debugger: SingleStep On Chip (PowerPC 8xx) v7.5 from Software Development System Inc.
How to configure SingleStep for MBX860?

Once installed Single Step MUST be configured for MBX860 target. To do so, copy the next files into the cmd directory of Single Step:
  • mbx860.cfg
  • mbxupm_40.dbg

These files can be found in //debian/arch1/tools/singlestep/mbx860/. The following lines are happened at the end of the sstep.ini file: 
echo "set mbx860 parameters"
alias _config "source ${cmdpath}mbx860.cfg"

MCB167

Which compiler/tool are supported?

Keil Compiler and Keil uVision debugger from Keil Software.
How do I download an executable file on the mcb167 board?

Just run gmake with the debug target: gmake -fkeil.mk debug. This will automatically run the uVision debugger of Keil Software with some default parameters. Then type load yourpgm.abs in the command line (prompted by >)

Note: there is only one serial link on the mcb167 board. It is both used for the debugger and the console (on uVision console). The other DB9 plugs ARE NOT usable serial links...
I got warning/errors at links (duplicated symbols, unresolved external symbols, ...). Any clue?

Check the 2 following points:

  1. Try shorter path names for NexGen Software products. You could use the subst command. For example:

    subst z: c:/home/nexgen/dev/
set NGOS=z:/ngos

  2. Do not compile several things at the same time, i.e. make sure to have a single instance of keil compiler running.
The library link step fails on Windows98. What's wrong?

The object list is too long. The windows shell command "echo" used to build the object list into a file seems to be unknown (e.g. the shell returns "unknown command").

Net186

Which compiler/tool are supported?

Paradigm C++ 5.00 (16-bit tool suite). Make sure NOT TO USE Paradigm C++ PRO 6.00 => check/change the value of your PARADIGM env variable.
How do I download an .axe (executable) file on the board?

After making sure that the monitor is running on the board (pdrom.hex in flash), that a serial cable links the board and your pc (115200 is fine), double clik on the .axe file.
This will launch Paradigm C++ 16 bit and automatically start to load the program in the target.
Can I download the program in FLASH?

Most of the time: no. The board has already a program in flash: a monitor that is started at boot time (pdrom.hex).
The Paradigm C++ debugger will try to establish a connection to this monitor.
I really want to overwrite the FLASH with my own .hex file. How do I do?

Open an hyperterm (I assume you are using correct COM), reset the board (white push button) and press 'a' on the hyperterm while the board is rebooting (the leds are blinking).
Then you should see a prompt on the hyperterm.
The flash is erased with command 'xa'.
A file can be loaded by using the transfert/send text file command.

RemotePC

Which compiler/tool are supported?

Paradigm C++ PRO 6.00. Make sure NOT TO USE Paradigm C++ 5.00 (16-bit tool suite) => check/change the value of your PARADIGM env variable. For example, if you have installed Paradigm C++ Pro into directory C:\usr\paradigmpro, type the following command
SET PARADIGM=C:\usr\paradigmpro
The variable PARADIGM is used by NexGen Sotfware's makefiles.
The file PDREM32.RTB is missing. How can I get it?

This file is the result of a compilation. So you can MAKE it, using Paradigm C++ Pro in the following way:
  • Launch Paradigm C++ Pro (click on continue on the license dialog box)
  • Open project file pdrom32.ide located in
    <ParadigmPro>\Pdremote.Rom\Protected\Boards\RemotePC
  • Make the top level target

This should produce the pdrem32.rtb file
How do I download an .axe (executable) file on the remote PC?

  • Launch Paradigm C++ Pro (click on continue on the license dialog box)
  • Click on Debug/load
  • Select your program and load it...
  • Hit Debug/Run

SEGGER

IAR M16c Compiler v1.33 from IAR Systems. Segger's Flasher v1.66g.

How do I download an .mot (executable) file on the board?

Launch Flasher from SEGGER. Goto to option/communication and select correct COM port.
Go to option/device, and select the device M30624FGxxx as well as Serial (in target) Interface..

Then got to File/opn to select your .mot file. Finally click on Target/Program & Verify.

DO NOT forget to read the readme file of ngos/hw/segger when using uC/OSii
Anything special about the power supply?

Yes! Make sure to provide a 9V tension with the - (i.e. "minus") in the inside part of the connector.
How to compile test programs?

Test programs must be compiled without the DEBUG option. This mean the iar.mk makefile MUST have DEBUG = no. DEBUG=yes is only used when debuging with the emulator since the startup file (cstartup.s34) need some change when debugging.

If the serial port is use as console, the STDIO_UART must be defined when compiling the m16csio.c file.
How to load test programs ?

To load the fresh hot test program:

  1. run the flasher_v166g.exe program (after copying it in the hard drive). and power on both target and flasher
  2. configure the communication ( Options -> Communication )
  3. configure the device as follow ( Options -> Device ) 
      Device    = M30624FGxxx
  Start Adr = 0xC0000
  End Adr   = 0xFFFFF
  Interface = Serial (In target)
  Speed     = Fast
  4. clear target flash ( F6 or Target -> Clear )
  5. load the test program ( File -> Open )
  6. program target flash ( F7 or Target -> Program & Verify )
  7. power off target
  8. change serial cable, load terminal program and configure it
  9. power on the target, the target show message in terminal program.
Witch serial port to configure?

The SEGGER card has only one serial port (UART1).
So the m16csio.c must be compiled with STDIO_UART=1 or the standard serial driver in m16cser.c must be configured using the NG_DEVO_SPEC1 = 1 option.
What is the maximum speed?

Serial console has been tested at 38400 bauds and was ok.
What is the uC/OS-II patch?

The OS_CORE.C file in uC/OS-II sources directory need to be patched to work with the M16C. Line 164 and 167, static OS_STK must be change to static NGnear OS_STK. This change is needed because the ISP (interrupt stack pointer) in the M16C processor is only 16bits wide and can't access all memory. This is a temporary working solution.

About NexGenOS tests: the 'os' and 'serial' tests programs for ucos-ii are fully working with stdio console at 38400bds for 'os' and serial shell at 38400bds for 'serial' ( no stdio). Since stdio use interrupts in m16c port, the lock shell command in 'os' lock the shell.