At the top of the “mobileGT_FLASH_commands.txt” file, does it have a
“fe fe000000 feffffff” command at the very top (or something similar)?
You may have to erase the flash area completely before you can program
into it reliably.
Thanks,
-Jay.
Nikolay Kristev wrote:
OK, at least the IPL is finding the OS image. However, as you
suspect, it does appear that the flash partition is not being
mounted correctly. Are you rebuilding any of these images
yourself, or are you just using binaries and S-Rec images that
were provided with the BSP? If you’re using all pre-existing
images, were you able to successfully flash the board previously,
or is this the first time you’ve flashed the board?
I use the binaries and S-RECs that came with the BSP. I haven’t flashed
the board before, when I received it the OS was already set up.
Acatually, a few days ago the board started giving out errors “File
system corrupted” and some partitions failed to mount, so I had to
reflash everything. I thought it might be that the FLASH is corrupted,
but so far dBUG doesn’t fail writing to it.
Did Motorola provide a build file with the BSP, which is used to
generate the dev.srec image? Based on the address that dev.srec
gets programmed to, it appears that that is the actual OS image.
If you have a build file, could you post it?
Yes, those were included in the BSP. Here is the build file for the OS
image:
[image=0x20000]
[virtual=ppcbe,srec -compress] .bootstrap = {
startup-total5200sdp -Dpsc3.115200.132000000
PATH=/proc/boot procnto-600
}
[+script] .script = {
These env variables inherited by all the programs which follow
SYSNAME=nto
TERM=vt100
HOME=/
PATH=./:/proc/boot:/sbin:/bin:/usr/local/bin:/usr/photon/bin:/ibmj9
LD_LIBRARY_PATH=./:/proc/boot:/usr/lib:/usr/local/lib:/usr/photon/lib:/usr/photon/dll:/ibmj9
SHELL=/bin/esh
LOGNAME=root
/proc/boot/devf-total5200sdp -s 0xfe000000,32M,0,64M,256K -r -u2 -b5
-t1 &
waitfor /sbin
waitfor /usr/lib
waitfor /bin
Start the serial on port 2.
/sbin/devc-16c654-total5200sdp -e -F -S -b115200 -c7372800 -u2
0x30000020^2,0 &
waitfor /dev/ser2
reopen /dev/ser2
display_msg Welcome to the Motorola Total5200 Development Platform.
display_msg Console started on port 2.
Load BestComm DMA tasks
display_msg Start BestComm tasks.
/sbin/bestcomm-task-load-total5200sdp -n 6 -m ff
display_msg Start the message queue manager.
/bin/mqueue &
display_msg Start the pipe manager.
/bin/pipe &
#display_msg Start the run control script.
[+session] /bin/ksh /proc/boot/rc
}
[type=link] /dev/console=/dev/ser2
[type=link] /proc/boot/libc.so=/proc/boot/libc.so.2
[type=link] /usr/lib/libcpp.so=/usr/lib/libcpp.so.2
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so.2
[type=link] /usr/lib/libsocket.so=/usr/lib/libsocket.so.2
[type=link] /usr/lib/libasound.so=/usr/lib/libasound.so.2
[type=link] /usr/lib/libm.so=/usr/lib/libm.so.2
[type=link] /tmp=/dev/shmem
[data=c]
[search="${QNX_TARGET}/ppcbe/lib"]
libc.so.2
Drivers:
[data=u]
[search="${QNX_TARGET}/ppcbe/sbin"]
devf-total5200sdp
/proc/boot/bootup.ksh = {
if [[ -a /etc/bootup.ksh ]]; then
/etc/bootup.ksh
fi
}
/proc/boot/rc = {
/etc/bootup.ksh is gone.
if [[ ! -e /etc/bootup.ksh ]]; then
ln -s /etc/bootup.config.ksh /etc/bootup.ksh
fi
This gives you a shell in case
/etc/rc is gone.
if [[ -e /etc/rc ]]; then
exec /bin/ksh /etc/rc
else
/etc/bootup.ksh
while /bin/true; do
/bin/ksh
done
/bin/shutdown -v -S system
fi
}
and the FS statements for the important images
driverlibs: [block_size=256k spare_blocks=0 mount=/usr/lib
min_size=4096K max_size=4096K perms=+r,+w,+x]
drivers: [block_size=256k spare_blocks=0 mount=/sbin min_size=2048K
max_size=2048K perms=+r,+w,+x]
ppcbe: [block_size=256k spare_blocks=1 mount=/bin min_size=4096K
max_size=4096K filter=“flashcmp -t ucl” perms=+r,+w,+x]
fsdev: [block_size=256k spare_blocks=1 mount=/ min_size=5120K
max_size=5120K filter=“flashcmp -t ucl” perms=+r,+w,+x]
The rest of theses build files is just what should be included in the FS
image, but if you think these are important, I’ll post them as well
Thanks,
Nikolay[/quote]
>
