Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
2 ratings:
 2.5 out of 5     Rate this Document

Setting Up the Hardware for the Axiom CMD565, eCos RAM Image Example Target

Primary Software: LabVIEW Modules>>Embedded Development Module
Primary Software Version: 1.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem: I have an Axiom CMD565 evaluation board. How do I set up the hardware for use with LabVIEW Embedded if I would like to use the Axiom CMD565, eCos RAM Image example target?

Solution:

Flashing the internal flash array with RedBoot



The Axiom CMD565, Axiom CMD565, eCos RAM Image target configuration expects the RedBoot boot loader to be present in internal flash array of the CMD565 board. RedBoot must be located in the external flash array and the board must be configured to boot from external flash. To produce this configuration, follow these steps:

1. Configure you board as shown on picture below. This is default the axiom configuration that allows to booting Axiom Monitor.




2. Connect COM1 to available COM port of your host machine. Make sure that you use straight cable. NULL modem cable will not work.
  
3. Launch AxIDE that comes with the board or other communication program (Tera Term) and open connection to serial port the board is connected to. Note that communication settings are: 9600, 8, N, 1, N
 
4. Power up the Axiom board. The Axiom Monitor should come up.

---------------------------------------------------
AXIOM CMD-5XX UTILITIES -- 561/3/5 release 02.08.08a
-----------------------------------------------------

1. Debug Monitor
2. On-Chip CMFI Flash Programming
3. External Flash Programming
4. Test Hardware

Select:
 

5. Press 2 to flash internal flash array
 
PM CONFIG SW 5 and 6 must be ON... press any key to continue...
Initializing Flash...

CMD-5xx board - 563/4/6 C3F Flash Programming (rev 3.1)
-------------------------------------------------------
E. Erase C3F Flash
P. Program C3F Flash from file
H. Program Hard Reset Configuration Word
Q. Quit to Menu

Select:
   

6. Press E to erase internal flash array
  Erasing Flash... 
 
7. Press P to program internal flash array
  Send Motorola S19 File Now... 
 
8. Hit the Upload button and browse for the redboot.s19 file located in the ..\resource\LabVIEW Targets\Embedded\ecos\cmd565\bin directory. It takes a few minutes to program internal flash.
 
9. Power off the Axiom board and configure dip switches and jumpers as shown below. Change the baud rate of your terminal program to 57600 bps.



10. Power on the Axiom board. The RedBoot monitor should come up.
  RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version CMD5xx/MPC5xx ROM-Startup - built 17:18:05, Mar 15 2004 

Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00400000-0x005fffff, 0x00400000-0x005f3fff available
RedBoot>
   

11. Now your board is configured and ready for use as the Axiom CMD565, eCos RAM Image target.

Running an application


 
1. You need two serial ports to run the example application. COM2 displays diagnostic information, COM1 is used to download built application. Make sure that you get RedBoot splash message on both COM ports. Note that both ports communicate at speed 57600 bps
 
2. Launch LabVIEW and switch to the Axiom CMD565, eCos RAM Image target
 
3. Launch the Embedded Project Manager by choosing Tools >> Embedded Project Manager...
 
4. Go to Target >> Target Options and make sure that download and debug serial ports are correct. Note that download serial port is COM port that is connected to the COM1 port on the Axiom CMD565 board.
 
5. Open terminal on COM port that is connected to the COM2 on the Axiom CMD565 board.
 
6. Create simple VI that prints something on diagnostic output using the One Button Dialog.vi. The string that is wired to the "message" terminal will be printed to stdout.
 
7. Add VI to the project, save, and build it.
 
8. Hit the run button (on Embedded Project Manager) to download and run built application. Terminal that is connected to diagnostic output should display message the VI prints.

Related Links:

Attachments:


ecos1.gifecos2.gif


Report Date: 09/14/2005
Last Updated: 05/09/2006
Document ID: 3PDG85HD

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit