18:18 <bryanp> Anyone ever come across the guaranteed size for barriers on a NAND design with rk3066 or similar? Like maybe 2048 size blocks might be inherently safer as it can be flushed in one go compared to 4096?

20:23 <bryanp> Was there someone looking for more rknand timing information awhile ago?

20:45 <bryanp> If I am getting SHA ERROR on recovery.img repack any idea what is wrong? Is it the rkcrc on the recovery kernel? Or is it the something else?

20:56 <bryanp> mkbootimg attributes were the cause

21:23 <bryanp> Real longshot but has anyone ever done a remote upgrade of the bootloader on a rockchip device?

22:26 <naobsd> bryanp: RK bootloader should be able to update itself via misc partition without PC

22:27 <bryanp> ok via the misc partition?

22:27 <bryanp> It gets difficult though because it doesn't seem to work with old nand kernel module as well. Might have to put upgrade in ram?

22:27 <naobsd> ah,

22:28 <naobsd> if you're updating bootloader from ver. 1.x to 2.x, I guess PC tool is required and reformatting entire raw NAND is required

22:29 <naobsd> btw, generally, we (linux-rockchip _community_) don't know detail about NAND and RK bootloader implementation :(

22:30 <naobsd> well, RK bootloader and RK binary modules

22:32 <naobsd> bryanp: if you want to know about "self update bootloader via misc partition", there should be a convert tool in SDK. I'll check it later

22:33 <bryanp> Ok that would be great. Thanks for the explanation

22:34 <bryanp> Might be able to load everything into the ram, flash bootloader and lowerformat then install upgrade from ram? No idea if its possible...