NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[natemcnutty]

Originally Posted by Lmiller1708

Every time you flash it's going to wipe everything. This is why I have never believed in using Task 29. It does the exact same thing.



For Ram Size we should use this. This is also posted a couple of posts back...
.equ RAM_SIZE, 0x0E600000

For the wiping of the last 24MB's of data this would make sense to me to just reduce the size of the userdata. I do see this issue after a reset by losing some data.

I do think we need to find out these values too...

.equ    LOAD_START,     0x10000000
.equ    RAM_START,     0x10000000
.equ    RAM_SIZE,     0x0E600000
.equ    INITRD_START,     RAM_START+0x00800000
.equ    KERNEL_OFFSET,  0x8000
.equ     XIP_END,     0x2ff000

Here is what I think they should be but it won't boot...

.equ    LOAD_START,     0x20000000
.equ    RAM_START,     0x20000000    <-----Not sure...
.equ    RAM_SIZE,     0x0E600000
.equ    INITRD_START,     RAM_START+0x00800000  <---- Does not make sense to me what this really does... Does RAM start before Main Memory?
.equ    KERNEL_OFFSET,  0x8000
.equ     XIP_END,     0x2ff000

I'm curious why we would use 230MB on RAM SIZE? If you are going for the maximum amount of RAM, we have 288 MB (some is used for graphics though) which should be 0x12000000. I personally think they limited the amount of RAM to speed up boot (less memory to map).

For RAM_START, I'm thinking that is the pointer to the starting memory address we work from (where everything starts loading into RAM). This would cause initrd to get loaded into memory at the offset mentioned above.

Also, did you manually hex edit the rhod_payload file? I've been reading through [TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS) [ONLINE] - xda-developers but am not all that excited about doing the math out