**** BEGIN LOGGING AT Sat Feb 15 02:59:57 2020 Feb 15 18:06:49 seems that busybox is broken Feb 15 18:07:04 Patch 0001-Remove-syscall-wrappers-around-clock_gettime-closes-.patch does not apply (enforce with -f) Feb 15 18:38:29 davidlt: it's ok in oe-core, check your other layers, e.g. meta-riscv is causing this Feb 15 18:39:08 JaMa, let me check if there is any busybox in meta-riscv Feb 15 18:39:29 ah, there is a bbappend Feb 15 21:04:09 davidlt: meta-riscv was waiting for oe-core patch, its fixed now please update Feb 15 23:02:59 tlwoerner, JPEW: any clue where tinker board stores its u-boot environment? I spent quite some time now trying to figure it out, even patched u-boot to output the offset but I still must be missing something Feb 15 23:03:09 trying to get fw_printenv from userspace to work Feb 15 23:14:52 Jin^eLD: there are usually seprate partitions fw_getenv fw_setenv get read them from userspace Feb 15 23:15:06 tinker might be different Feb 15 23:15:33 khem: it has a bunch of partitions as defined in the rockchip wiki but its totally unclear where the env goes Feb 15 23:15:47 I ended up looking for it via hexdump Feb 15 23:15:59 but using that offset did not help Feb 15 23:16:01 what all partitions are there perhaps I can remember something Feb 15 23:16:35 http://rockchip.wikidot.com/partitions Feb 15 23:16:50 I think I tried pointing fw_env.config to each of them... Feb 15 23:17:48 is it not in gpt ? Feb 15 23:17:58 perhaps somewhere towards end ? Feb 15 23:18:56 I should see it when dumping, right? afaik its just key-vaue text with a crc? Feb 15 23:20:23 I don't think its there... Feb 15 23:23:15 if I look for those strings by dumping the image I can find them at 0x8483E9 Feb 15 23:23:43 which to be honest does not make much sense to me Feb 15 23:24:20 oh actually it might... the table in the link is in sectors Feb 15 23:24:36 so that offset would be somewhere in the loader 2 partition Feb 15 23:30:24 allthough possible that I only grepped out the strings compield into u-boot / fallback env Feb 15 23:36:10 I am pretty sure the environment is here: hexdump -s 4161536 -n 32764 -C /dev/mmcblk1 Feb 15 23:36:39 fw_env.config wants sectors, right? so that'd be /dev/mmcblk10x1fc00x40 Feb 15 23:36:54 but fw_printenv still gives me Cannot read environment, using default Feb 15 23:37:21 doh I think my paste went wrong, I meant to write: /dev/mmcblk1 0x1fc0 0x40 Feb 15 23:52:22 got it... why do I always take the hard route? :) Feb 15 23:52:44 it was right there in the u-boot cofiguration Feb 15 23:52:47 (0x3f8000) Environment offset Feb 15 23:52:55 (0x8000) Environment Size Feb 15 23:53:22 and fw_env.config needs to be like this: /dev/mmcblk1 0x3f8000 0x8000 Feb 15 23:53:36 ^^^ that's for the tinker-board-s should anyone else be stuck with the same question **** ENDING LOGGING AT Sun Feb 16 02:59:57 2020