ChanServ changed the topic of #linux-cros-arm to:
tobhe has joined #linux-cros-arm
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-cros-arm
<Jasper[m]> Hmm, haven't looked directly into coreboot in a sec, but do any of you know what tools to use to alter settings of coreboot in a flash dump?
<WeirdTreeThing[m]> all of the settings are compiled into coreboot
<WeirdTreeThing[m]> what do you want to change?
<Jasper[m]> @jenneron and a pmos user have tried to get usb boot enabled on Smaug/Dragon/Ryu using crossystem, but that didn't work
<Jasper[m]> I'm not entirely familiar with how these settings are saved on the device. I know you can't do it on the "normal" coreboot distribution since it's in nvram. But I figured I'd ask
<Jasper[m]> That device is also bricked btw, the default payload expected some partition format on eMMC and now doesn't want to go into fastboot anymore hahahaha
<WeirdTreeThing[m]> oh you mean depthcharge settings
<WeirdTreeThing[m]> those are stored in the RW_NVRAM flash region
<WeirdTreeThing[m]> tbh i dont know much about that device other than it uses depthcharge
<WeirdTreeThing[m]> i have no clue how android booting is implemented
<Jasper[m]> <WeirdTreeThing[m]> "i have no clue how android..." <- iirc it's a very rough payload that implements some regular fastboot commands, but it'll still need a depthcharge image
<Jasper[m]> It doesn't use cgpt
<Jasper[m]> <WeirdTreeThing[m]> "those are stored in the RW_NVRAM..." <- On SPI? The person trying to modify the image can't write to the chip for some reason (when removed from the motherboard)
<WeirdTreeThing[m]> yes on spi
<WeirdTreeThing[m]> <Jasper[m]> "iirc it's a very rough payload..." <- yeah i looked at the depthcharge fastboot implementation and it doesnt look to have many commands
<Jasper[m]> WeirdTreeThing[m]: Is there a way to alter those from a flashdump (assuming they are in there)
<WeirdTreeThing[m]> afaik no tool currently exists for that
<WeirdTreeThing[m]> but I am looking into it