<hgs>
this file was taken from chroot/debootstrap/debootstrap.log
<beeble>
all this size change warnings don't look good
<beeble>
if you are just building the base system anyway, just do it by hand as suggested last time. takes you 10mins and you will see if any stage fails immediately
kaspter has quit [Quit: kaspter]
nots has quit [Quit: Page closed]
Kamikaze84 has joined #linux-rockchip
kaspter has joined #linux-rockchip
<Kamikaze84>
Hi, I was here the other day but was literally the only person that was active in the channel for the whole day - so just asking my questions again:
<beeble>
Kamikaze84: does your current u-boot support sd card access?
<beeble>
check mmc list if it lists the sd card controller
<Kamikaze84>
Wow you responded before I managed to ask the questions again, haha. Umm so I have upgraded to the latest firefly provided eMMC image, I read somewhere that sometime back in May 2017 they supported SDCard boot via the miniloader, but I am not certain if that was only for a particular release or all subequent releases worked.
<Kamikaze84>
good information on this board is fairly hard to come by
<beeble>
the miniloader part isn't that important. it depends on how u-boot is configured on that board. miniloader loads u-boot
<beeble>
if it supports the sd card you just have to load the kernel+fdt from the sd card with setting a proper bootcmd line
Kamikaze84_ has joined #linux-rockchip
<Kamikaze84_>
beeble: ok thanks. but how would I specify a bootcmd line with the existing image on the eMMC? Is there something documented as to how to do this?
<beeble>
setenv bootargs <your kernelcommandline>
Kamikaze84 has quit [Ping timeout: 260 seconds]
<beeble>
the essential part is to change the root=/dev/mmcblkXpX part
<beeble>
that should point to the sd card
<Kamikaze84_>
ok cool
<Kamikaze84_>
so i'll have to hook up a serial line to get to the u-boot, or can I reflash just the u-boot on the eMMC with new params?
<beeble>
to change that settings it is easiest to do it interactive on the u-boot shell
<beeble>
as said, check if you have sd card support. if not you will have to build your own u-boot
<Kamikaze84_>
will do. can it save permanent env changes from there, i assume with a command like saveenv (IIRC?)
<beeble>
exactly
<Kamikaze84_>
thanks again. i will give it a shot! if i need SDCard support, I might just find that older image and try flash that to eMMC and see if it works, rather than compiling my own u-boot, as I'm not sure what offset it would need to be flashed against...
<beeble>
we skipped the part on how to load the image. but you will have to add something like load mmc 1:1 $kernel_addr_r Image && load mmc 1:1 $fdt_addr_R rk3399-firefly.dtb; booti $kernel_addr_r - $fdt_addr_r
<beeble>
as your bootcmd env. that's out of my head so you have to check if 1:1 is the right device may be 0:1 but mmc list will tell you which one is right
<beeble>
i could tell you the offsets for mainline u-boot but not sure about the vendor stuff if it's padded or not
<beeble>
if you erase the emmc you can also just put the bootloader on the sd card
<Kamikaze84_>
i've been considering that, but I'm not confident that I could get that to work... e.g. if I had issues with booting from the sd card, I would be out of my depth by that point, and shorting pins to get into maskrom mode sounds risky - pretty sure I've read at least one report where a guy thought he might have fried his board by accidentally shorting nearby pins.
<beeble>
an erased emmc would mean it falls back to maskrom without a sd card inserted anyway. but if you have doubt that you will be able to short the pins correctly i will not suggest it
<beeble>
are this pads really that bad? never seen them myself