**** BEGIN LOGGING AT Thu Feb 06 02:59:57 2020 Feb 06 12:34:37 https://marcin.juszkiewicz.com.pl/fosdem/ - covers all years with videos (2015-2020) Feb 06 13:54:47 tlwoerner: well, I think it has both, an sd-card port and emmc (the one "soldered" on the board) Feb 06 13:55:01 and you have a jumper to tell the boot process to boot from sdcard or from the internal flash Feb 06 13:55:55 so tinker-board should have emmc...?! :) how did you flash it? Feb 06 13:56:21 Jin^eLD: aaaaahhhhhh Feb 06 13:56:27 you have the tinker board "C" Feb 06 13:56:30 or in other words... if you flashed it to sdcard assuming the board has no emmc then it probably worked, this scenario works for me as well Feb 06 13:56:45 oops, Tinker Board "S" Feb 06 13:56:53 http://linuxgizmos.com/asus-tinker-board-s-adds-16gb-emmc-and-more/ Feb 06 13:56:55 oooh ok sorry, I should have mentioned that, indeed, its an "S" I think Feb 06 13:57:08 actually I did not know there were emmc-less versions :) kinda missed that Feb 06 13:57:10 ahh, good to know. i wasn't aware there was a newer model Feb 06 13:57:30 OK, so that means you tested with the sdcard, right? Feb 06 13:57:32 that works for me too Feb 06 13:57:50 yes, that's all my board has Feb 06 13:58:01 https://www.asus.com/ca-en/Single-Board-Computer/Tinker-Board/specifications/ Feb 06 13:58:03 but I think the u-boot that we build misses something, because it won't work with emmc Feb 06 13:58:12 yes, that makes sense Feb 06 13:58:34 probably also the kernel, when I boot via sdcard I don't see emmc from userspace either Feb 06 13:59:05 yes, there's probably a separate defconfig and/or DT spec for the "S" models Feb 06 13:59:41 so should the "s" be another machine conf? Feb 06 13:59:49 yep, there it is Feb 06 13:59:54 with those features enabled in the respective defconfig? Feb 06 14:00:53 yes Feb 06 14:01:23 we'll need a separate MACHINE in meta-rockchip, not a bit deal. i can try blindly putting one together (i don't have an "S") Feb 06 14:01:30 or you can give it a shot ;-) Feb 06 14:02:21 if you know what exactly to enable that'd help me, but I can also have a look myself Feb 06 14:02:25 the defconfig for u-boot is named "tinker-s-rk3288_defconfig" Feb 06 14:02:28 https://github.com/u-boot/u-boot/blob/master/configs/tinker-s-rk3288_defconfig Feb 06 14:02:33 oh its alraedy there Feb 06 14:03:04 I think I could try adding it myself then and hopefully come up with a patch if it all works Feb 06 14:03:38 yes, we just need a new meta-rockchip/conf/machine/tinker-board-s.conf Feb 06 14:04:24 OK, I'll do it then Feb 06 14:04:38 thanks for the hints :) Feb 06 14:05:40 update the UBOOT_MACHINE and KERNEL_DEVICETREE Feb 06 14:05:53 u-boot: tinker-s-rk3288_defconfig Feb 06 14:06:06 kernel: rk3288-tinker-s.dtb Feb 06 14:06:14 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts?h=v5.5.1 Feb 06 14:07:18 cool, thank you, I'll report back as soon as I tested it Feb 06 14:07:47 thanks! Feb 06 14:09:06 ...then buy another "S" and ship it to me ;-) hahhahahah lol Feb 06 14:13:11 hehehe Feb 06 14:15:10 do you have a procedure for flashing the eMMC? flashing eMMCs is usually cumbersome (proprietary tools, fiddly procedures...) Feb 06 14:17:06 they solved it nicely... but you need a u-boot with UMS support (uboot mass storage?) Feb 06 14:17:56 you have several options, if your u-boot in emmc can do ums, you connect the micro usb to your pc instead of just a power adapter and emmc will be shown as mass storage Feb 06 14:18:04 so you can just dd your image onto it Feb 06 14:18:19 if you screwed up your uboot on emmc you can set the jumper to boot from sdcard Feb 06 14:18:47 there again, you can either have your usb cable connected to the pc - then it will present the emmc as mass storage to your pc Feb 06 14:18:54 Jin^eLD: You'll also need to change the kernel boot args in the kickstart file Feb 06 14:19:02 or you can just boot via sdcard, wget your image and dd it Feb 06 14:19:43 JPEW: probably depends on how it will get enumerated? i.e. if setting the jumper to sdcard will change the order of appearance Feb 06 14:19:58 otherwise if mmcblk0 is always the boot device then it probably could use the same args? Feb 06 14:20:17 Jin^eLD: Usually it just changes what emmc the SoC boots from Feb 06 14:20:45 I'll have a look at all of it after (late) lunch Feb 06 14:21:11 now that I know why emmc was not found and how to make it appear it should not be too hard to configure everything Feb 06 14:22:51 yesterday I was mostly confused because it did not find the emmc at all and at that point I did not realized that I compiled the image for an emmc-less version Feb 06 14:22:59 so now it all makes sense of course Feb 06 16:35:47 so if the layer index is going to put this message out "Your account has been locked out. Please contact the admin." is should indicate who the admin is. Feb 06 16:40:24 tlwoerner: one thing I am noticing - on Yocto we don't seem to have this UMS feature enabled in u-boot, i.e. when I connect the board to my PC and have a yocto image flashed Feb 06 16:40:29 it won't show up as mass storage Feb 06 16:49:13 btw thats a bit odd, are two root statements valid at all? Feb 06 16:49:14 [ 0.000000] Kernel command line: root=/dev/sda7 rootwait console=tty1 console=ttyS2,115200n8 rw root=/dev/mmcblk0p7 rootfstype=ext4 init=/sbin/init Feb 06 16:58:34 when booting from sdcard it still does not see emmc, but u-boot itself seems to know about it now Feb 06 16:58:59 I have a feeling that further tuning of those defconfigs will be required, just taking the stock ones for the -s model does not seem to do the trick Feb 06 16:59:22 when trying to boot from emmc I get stuck in a loop, it tries to load the kernel but them jumps back to u-boot Feb 06 17:04:24 ah, ums is in u-boot but I guess it has to be started manually Feb 06 17:04:32 i.e. in yocto-built u-boot Feb 06 17:04:44 mmc 0 is the internal emmc Feb 06 17:04:58 I wonder why it won't boot properly though Feb 06 17:07:29 basically it stops at [ 4.655352] Waiting for root device /dev/mmcblk0p7... Feb 06 17:08:14 ok thats odd, so for u-boot emmc is mmc0 but for the kenrel its mmc1? Feb 06 17:08:54 https://paste.ee/p/RQvn9 Feb 06 17:12:22 JPEW: I guess you were right about the order after all Feb 06 17:12:26 :) Feb 06 17:14:04 I now wonder if one needs to build two images depending on where it is going to be used - one for sd and one for flash? since the kernel command line will differ... Feb 06 17:22:40 I guess a few questions need to be clarified before I can come up with a patch, bug generally it seems to work, using those configs allowed to boot from emmc after all (+command arg tuning) Feb 06 18:24:21 Jin|away: Yes, you might need a different wks file for emmc/sd bood Feb 06 18:49:28 Jin|away: yes, separate images (depending on whether it's going to be used on uSD or eMMC) would be required, and is how other BSP layers handle it (currently) Feb 06 18:50:21 Jin|away: multiple MACHINEs get defined, each with the settings required for that configuration, and therefore multiple builds are done Feb 06 18:50:42 (even though it's the same baord) Feb 06 19:43:09 n Feb 06 22:28:20 n Feb 06 22:28:52 JPEW, tlwoerner: I thought one could flash the same armbian on sdcard or emmc and it would work? hmm Feb 06 22:29:04 OK, I'll create two wks images then **** ENDING LOGGING AT Fri Feb 07 02:59:57 2020