View Single Post
  #1208 (permalink)  
Old 02-11-2011, 09:52 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 01-07: Panel power on/off fixes

Lmiller, can you check your script.. something doesnt make sense

Code:
#
compile tinboot
cp tools/rhod_payload os.nb.payload
echo "Inserting tinboot into payload"
cat xip/$1 >> os.nb.payload
mv os.nb.payload.NEW os.nb.payload >> tools/log
echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin OS.nb.payload OS-new.nb.payload >> tools/log
echo "Creating os.nb portion of nbh"
tools/nbmerge < OS-new.nb.payload > OS-new.nb
echo "Creating NBH"
wine tools/yang.exe -F ruu_signed.NBH -f OS-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log
Look at lines 4 and 5. First you append the xip onto os.nb.payload, but the next line you overwrite it with os.nb.payload.NEW ?

let me know if im reading this wrong since i dont know where os.nb.payload.NEW comes from.
__________________
Reply With Quote