EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: RTEMS booting problem under uCdimm5282 module.
From: Eric Norum <[email protected]>
To: Kiman Ha <[email protected]>
Cc: [email protected]
Date: Thu, 2 Jun 2005 08:28:01 -0500

On Jun 2, 2005, at 2:23 AM, Kiman Ha wrote:


Hi,

How to generating procedure of bootable binary file for uCdimm5282 RTEMS?

I tried to boot under uC5282 module which epics example code test5282.obj,
it is generated by epics makefile.

That is not the correct file to download to the uCdimm5282. You need to download the <top>/bin/RTEMS-uC5282/test5282.boot file which should have been produced when you built the EPICS application.


test8252.obj file is put to the uCdimm5282 memory using tftp.
And typed goram, but target was not responsible.
Does it need converting binary format for executing under uC8252 module?

Yes, and the required conversion should have been done.



If anyone has an experience pleas let me know.



======================================================================= Here is a section of the README for the 5282:


Downloading the image to the board.
===================================
The bootable image is generated by the make-exe target in the bsp makefile. It
generates a simple stripped binary file which is downloaded over the ethernet
port into RAM then executed or programmed into flash memory.


1) Power up the uC5282 board. A dump of some memory maps is produced
   followed by a prompt.

2) (first time only)
Set the uC5282 board Internet configuration:
setenv IPADDR0 www.xxx.yyy.zzz (Your board's address)
setenv NETMASK ppp.qqq.rrr.sss (Your local network address mask)
setenv HOSTNAME somename (Your board's name)


3) Type 'tftp<CR>'

4) Run 'tftp' on your host machine:
tftp> binary
tftp> connect www.xxx.yyy.zzz (Your ucDIMM's address)
tftp> put someFile.exe (or someFile.boot if you're using the EPICS build system)


5) When the file has downloaded press the <ESC> key to terminate
   the uCDIMM tftp command.

6) Type 'goram<CR>' to start the downloaded program, or type 'program<CR>'
to burn the code onto the uCDIMM flash.


EPICS Bootstrap Information
===========================
The EPICS startup code uses the following environment variables. If an
optional environment variable is missing the value in parentheses will be used.
All Internet addresses must be given in 'dotted-decimal' format.
HWADDR0 - Ethernet hardware address.
IPADDR0 - Internet address (192.168.0.2).
NETMASK - Local network address mask (255.255.252.0).
HOSTNAME - Internet host name (iocNobody).
GATEWAY - Internet address of gateway machine (NULL).
SERVER - Internet address of NFS server (192.168.0.1).
NAMESERVER - Internet address of DNS server (SERVER).
DOMAIN - DNS domain name (precompiled value from CONFIG_SITE).
NTPSERVER - Internet address of NTP server (SERVER).
BOOTFILE - Path to executable (epics/iocNobody/bin/RTEMS-uC5282/myApp.boot).
CMDLINE - Path to startup script (epics/iocBoot/iocNobody/st.cmd).
NFSMOUNT - NFS information: www.xxx.yyy.zzz:/remote/path /localpath
A : can also be used to separate the remote and local paths.
If NFSMOUNT is not set, SERVER will be used as the NFS server,
and the remote and local paths will be taken from the first
component of CMDLINE. If CMDLINE does not begin with a /
then '/tftpboot' is prepended to the remote path. This allows
a remote TFTP and NFS server to be handled transaparently.



The EPICS/RTEMS startup code can get the application startup scripts, '.db' and .'dbd' files from a flash in-memory filesystem image. This allows an IOC to start up even if the network is not operational. To create such an image simply tar up the required files and concatenate the tarball to the end of the application xxxxx.boot file, then transfer this image to the uCdimm flash memory.
Here's the script I use to perform this operation:
#!/bin/sh


set -ex

case "$#" in
    2)  name="$1" ; boot="$2" ;;
    *)  echo "Usage: $0 iocname boot_image" >&2 ; exit 1 ;;
esac

make -w

#
# Create a standalone (FLASH-based) IOC image
#
rm -rf tarball
mkdir tarball
cp -r db dbd tarball
sed -e '/epicsEnvSet[^A-Za-z0-9_]*TOP[^A-Za-z0-9_]/s/.*/epicsEnvSet(TOP,"\/")/ ' "iocBoot/${name}/envPaths" >tarball/envPaths
cp "iocBoot/${name}/st.cmd" tarball/st.cmd
(
cat "$boot"
(cd tarball ; tar cf - *)
) >"$boot:$name.image"



-- Eric Norum <[email protected]> Advanced Photon Source Argonne National Laboratory (630) 252-4793


References:
RTEMS booting problem under uCdimm5282 module. Kiman Ha

Navigate by Date:
Prev: RTEMS booting problem under uCdimm5282 module. Kiman Ha
Next: how to import Oratcl to et_wish huangsong
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RTEMS booting problem under uCdimm5282 module. Kiman Ha
Next: how to import Oratcl to et_wish huangsong
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·