Quote:
Originally Posted by [ACL]
there is really no need right ? We are sending the imgfs in the payload. Vogue adds this separately through tinboot. So we we need to mod our payload and strip the imgfs portion so we can add it to tinboot as well. We can actually use their emtpy imgfs which will just wipe one block. I dont think the partition table on the vogue even matches the mtd parts.
I can try to snoop the mtty tonight and see what the whole flash process looks like.
who isnt working right now? come on someone lets try this !!!
|
Yeah, what I am looking at is finding out exactly where the NAND starts so we can put tinboot at the very beginning and maximize the amount of space we have to use on NAND. I guess it doesn't really matter at this point since we know the locations we are writing to are valid.
I guess we could try using the vogue's current tinboot build, make the MTYPE change, mem start change and other changes and see how it works. I was in the process of doing that last night just to see if it worked by chance, but I got pulled away by the wife. Unfortunately, we have a dinner party at some friends tonight, so I won't have a computer all night
