IRC logs for #automotive for Friday, 2019-05-03

OutBackDingofury: what image did you use?00:42
furyOutBackDingo: built the regular agl-demo-platform image00:42
furyCheck my pastebin to see the full list of commands I used, from 0 to flashing the image on SD card00:43
furyfollowed the docs mostly (to make sure they're still good)00:44
OutBackDingofury: i wonder if this has something to doo with xzcat on fedora00:45
OutBackDingofury: nano site.conf ??00:46
furyonly difference from the docs I think was that my customizations to the build went into site.conf instead of local.conf (I copy the file around to my different build dirs) and that I added direct / progress flags to the dd in a futile attempt to get an accurate indication of how much time left to finish flashing the card (Linux aggressively caches the xzcat write)00:46
furythat's where I put my DL_DIR and SSTATE_CACHE00:46
OutBackDingook00:46
OutBackDingofury: so im starting to wonder if im hitting the tar issue on Fedoa 3000:48
OutBackDingonothing else exlains it00:48
furyCould be. What version of tar?00:48
OutBackDingo1.32 FFedoa 3000:49
furythat ought to be new enough O_o00:49
OutBackDingoi build it on Debian 9, scp it to my workstation to run xzcat agl-demo-platform-raspberrypi3.wic.xz | sudo dd of=/dev/sde bs=4M oflag=direct status=progress00:50
furyDoes your Debian 9 have an SD card slot?00:51
furyYou may be able to narrow it to an xzcat issue by unzipping it from Debian 9 (into just .wic) and copying the file over, sudo dd if=filename.wic of=/dev/....00:53
furyhave you tried one of the images from the AGL download site?00:54
furyif the unzipped file isn't any different in the end than if you unzipped in fedora tho, that wouldn't be the issue00:55
OutBackDingofury: ots a VM00:56
furyah ok00:56
OutBackDingofury: same md5sum on both after xz -d on debian and fedora01:00
furyOutBackDingo: Unmounting sde* prior to dd?01:01
furyGive it a sync after the dd returns, it may not necessarily have finished writing, too...which the oflag direct is supposed to fix, buuuuut that wasn't my experience today >.>01:02
OutBackDingook  sudo dd if=agl-demo-platform-raspberrypi3-20190502115937.rootfs.wic of=/dev/sde bs=4M oflag=direct status=progress01:05
OutBackDingofury: nope, same result01:09
furyhttps://download.automotivelinux.org/AGL/snapshots/master/latest/raspberrypi3/deploy/images/raspberrypi3/agl-demo-platform-crosssdk-raspberrypi3.wic.xz01:10
furyI recall Debian is notorious for hanging onto old versions...what tar version in the VM?01:15
OutBackDingodownlooading, ill even use a new sddccard... no idea01:15
furydid you say you'd tried raspbian earlier on that card and it was fine?01:15
OutBackDingoyupp01:25
OutBackDingonothing... same result....02:06
OutBackDingofury: guess ill reboot and try thhis in ubuntu02:07
*** ric96 has quit IRC02:10
*** ric96 has joined #automotive02:12
*** AlisonChaiken has joined #automotive02:36
OutBackDingofury: breaking out etcher, under ubuntu lets see what we get now02:44
OutBackDingofury: nope, still no joy, nothing, multiple sdcards, multiple images, all sit at u-boot02:57
OutBackDingotried dd, xzcat, etcher, on fedora and ubuntu02:57
OutBackDingoeven tried it on a pi3 B wount even get to u-boot03:00
OutBackDingoim starting to think its the board, however it boots raspbian fine04:34
*** montjoie has quit IRC05:07
*** montjoie has joined #automotive05:09
*** toscalix has joined #automotive06:06
*** kbroulik has joined #automotive06:34
OutBackDingoand now ive verified yocto core-image-minimal boots fine on the this board....06:50
OutBackDingosooo... wats missing for AGL to not be working on a board that rasbian and yocto boot fine on06:50
GuyElpotatoOutBackDingo, Stupid question but what is the size of your SD card ?07:13
OutBackDingoGuyElpotato: 16/32GB07:15
OutBackDingoive tried many07:15
OutBackDingoa couple 16gb, a couple 32gb07:16
OutBackDingoeverything else works fine but AGL :)07:16
GuyElpotatoOk because I had this same kind of problem with my SD card which was too small for the agl-image-crosssdk07:47
OutBackDingoGuyElpotato: well... theyshould be large enough... really hard to pinpoint this issue07:53
OutBackDingoAGL just refuses to boot, sits at the u-boot promt07:53
OutBackDingoeverything else boots fine from the same cards07:53
GuyElpotatoThe prompt uboot scrolls in a loop or you can write commands ?07:54
OutBackDingoGuyElpotato: cant do anything no serial console no keboard acvtivity... so it just siteszs there u-boot:08:00
francesco_kinHi all, how can I solve the problem about CMakeAfbTemplates during the compilation of helloword-html-application? CMake Error at conf.d/config.cmake:163 (include):08:07
francesco_kin  include could not find load file:08:07
francesco_kin    CMakeAfbTemplates08:07
francesco_kinCall Stack (most recent call first):08:07
francesco_kin  CMakeLists.txt:22 (include08:07
francesco_kinI have already sourced /opt/agl-sdk/7.90.0+snapshot-armv7vethf-neon-vfpv4/environment-setup-armv7vet2hf-neon-vfpv4-agl-linux-gnueabi and /etc/profile.d/agl-app-framework-binder.sh08:08
claneysfrancesco_kin, this indicates that you miss the CMake module.08:08
claneysYou should find it under /user/share/cmake/Modules (redhat like distro) or /usr/share/cmake-x.y/Modules (debian like distro)08:09
claneysif you want to compile natively08:09
claneysOk so you are using the SKD08:09
claneysSDK08:09
francesco_kinclaneys, "which cmake" gives /usr/local/bin/cmake08:10
claneysThis isn't good08:11
claneysit means that you aren't using the CMake from the SDK08:11
claneyswhich should be in ${OECORE_NATIVE_SYSROOT}/usr/bin/cmake08:11
claneysalso you should find the CMakeAfbTemplates under ${OECORE_NATIVE_SYSROOT}/usr/share/cmake-x.y/Modules08:12
claneysfrancesco_kin, can you send us the result of 'env' command please.08:14
francesco_kinclaneys, ok. Can I create a symbolic link in usr/local/bin to point to the right cmake or I should08:15
francesco_kinclaneys, ok, https://paste.ofcode.org/YZvGkzdhDtdY2zfjvPiBgu08:15
*** jobol has joined #automotive08:19
francesco_kinclaneys, with a symbolic link to the right cmake in the sdk, compilation works and the make creates the wgt08:29
claneysfrancesco_kin, ok, I never used this SDK only Renesas Gen3 ones and intel/qemu08:32
claneysbut for what I saw either you source your environment setup file from a terminal and launch the build from another so you don't share the environment either there is a problem with the SDK because your should have mabny environement variable pointing to the SDK installation path08:33
*** leon-anavi has joined #automotive09:55
*** toscalix has quit IRC10:39
OutBackDingoleon-anavi: i have no idea why you two can get it booted however i cant11:44
leon-anavihi OutBackDingo, have you reported the issue in JIRA?12:47
leon-anaviI tried it out recently but in the mean time there have been some changes in master12:47
OutBackDingoleon-anavi: fury said    he tried master last night and it worked for him... i also tried from 2 weeks ago aand same u-boot issue, everything else i put on the board works, but if fury states master from lasst night works.. i have to wonder.....12:53
OutBackDingoleon-anavi: so i honestly cant claim a bug, if he states its functional for him... but im seeing differently othher then to state the symptoms i see12:54
OutBackDingoif someone else also saw it id be more coonvinced its a bug... righht now im simply convinced its not functional on "my board"12:55
furysomething's gotta be wonky about the build host if it's building the image but it's not working, that's still a bug really, but it will be tricky to pinpoint why. Debian 9 and Ubuntu 18.04 should be so similar as to create identical images, except that I know Debian keeps older packages around longer12:55
OutBackDingobut he saaid his works12:55
OutBackDingoive built on both Debian and Ubuntu .... same12:55
furybut if you downloaded from AGL and that still had the same issue, now I don't know12:55
OutBackDingoyupp.. 4 different images,,,, same issue12:56
OutBackDingo2 from AGL, and 2 i built12:56
OutBackDingofury: send me the one you have12:56
furyDid they change something on the Pi? My 3B+ is a few months old now...12:56
leon-anaviOutBackDingo, don't hesitate to open a JIRA issue even if it is not a bug this way we will have a track and it will be easier for other people encountering similar issue in future12:57
furyhmm, was trying to think where I could upload that. I don't immediately have a web server I can just drop a file into, though I could probably whip one up12:58
leon-anaviOutBackDingo, what power supply are you using for the pi?12:58
OutBackDingoleon-anavi: 5v 3000Ma12:59
OutBackDingoermm LOL mA12:59
OutBackDingofury: fileshare :)13:00
OutBackDingoi could create you an sftp account on a vm i have13:01
furydoh. We have a Citrix Sharefile. Of course. I spaced it. Gimme a few mins to upload13:01
OutBackDingoi could say a bad word also... mega :) or gdrive ... LOL13:01
OutBackDingofury: ahhhh ok cool13:02
leon-anaviOutBackDingo, this power supply should be good13:07
leon-anaviOutBackDingo, do you get any output on the serial console when you have this problem?13:07
OutBackDingoleon-anavi: works for yocto and raspbian no issues13:07
OutBackDingoleon-anavi: nope13:07
OutBackDingoi did test both yocto core-image-minimal and raspbian they booted fine13:08
OutBackDingoalso curious what his build host is.... i tried Debian 9 and ubnt 18.04 image built ok.... just refuses to boot13:08
leon-anaviOutBackDingo, raspbian is quite different, however core-image-minimal BSP from meta-raspberrypi is the same as the one we use in AGL (of course depends on the Yocto/OE release and the branch of the layer)13:09
fury18.04, just reinstalled it a few days ago in a new drive13:09
leon-anaviI am building on Ubuntu 16.0413:09
OutBackDingoleon-anavi: Yocto Thud built today13:09
OutBackDingoleon-anavi: i have a phot of the u-boot screen... want it ? :)13:12
OutBackDingoleon-anavi: just confirmed both yocto thud meta-raspberrypi and AGL meta-raspberrypi are at the same commit13:18
OutBackDingoboth have same commit 2b3693ea3a871619624ee8ebf1ad946915eb1aa8 referencing sdcard_image-rpi: Format boot partition as FAT3213:19
OutBackDingoCloses: #38213:19
OutBackDingogit show13:20
OutBackDingo-    mkfs.vfat -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img $BOOT_BLOCKS13:20
OutBackDingo+    mkfs.vfat -F32 -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img $BOOT_BLOCKS13:20
OutBackDingolooks negligable13:20
furyOutBackDingo: i can't imagine this'd work if none of the other AGL images you've tried have, but here it is anyway: https://radiosound.sharefile.com/d-sde8d5b54f564cad913:30
furysame image i flashed onto my pi last night13:30
OutBackDingofury: it is possible, though i doubt im having any environmental issues "building" or otherwise....13:33
furyi'm willing to bet something changed in the pi 3b+ unannounced, if this doesn't work13:33
furybut i don't know why yocto core image minimal woudl work and this wouldn't O_o13:34
OutBackDingoive had my board maybe 3 months, made in UK ... dount see a board rev on it though13:35
OutBackDingoand ive never really had issues booting anything yocto on it13:36
furymine's a little over 5 months old13:36
OutBackDingo-rw-r--r-- 2 dingo dingo 369128796 May  3 13:44 tmp/deploy/images/raspberrypi3/agl-demo-platform-raspberrypi3-20190503024434.rootfs.wic.xz images appear at least the same in size..13:37
OutBackDingofury: and your building master?13:37
OutBackDingolast updated ?13:37
leon-anaviOutBackDingo, you can attach a photo in JIRA. Log form the serial output is better if there is none, photo is better than nothing :)13:38
OutBackDingohrmm your image name is a little different then mine13:38
furymy repo synced 1:20pm eastern, last download completed probably an hour later13:39
furyI grabbed from the symlink13:39
furyit links to a similar looking .rootfs.wic.xz file but it was easier to manually type into the scp command :)13:40
fury1:20 pm eastern yesterday, that is13:40
furyI know some things do a git autorev which makes a reproducible build a little tricky but the alternative is an update to the recipe file and the manifest file every time any of the recipes change, and from what I've seen they tend to save those specific rev pinnings for release branches13:43
OutBackDingook, mine was last synched later then that.... did mine this AM... and im maybe 12 ahead13:43
OutBackDingoermm 12 hours timezone wise :)13:44
francesco_kinwhy I don't see can0 in /dev (dra7xxEVM5777) ?13:58
OutBackDingofury: nope same results....13:58
francesco_kinI'm using AGL 6.0.5 version13:58
*** GuyElpotato has quit IRC14:09
OutBackDingofury: my board rev states a020d3 in cat /proc/cpuinfo14:19
OutBackDingofury: i find odd also the first line printed says14:23
OutBackDingoNet: no ethernet found14:23
*** AlisonChaiken has quit IRC14:29
khilman dl9pf : not sure what's going on with ci-management gerrit, but i see you merged that ci-management patch in gerrit, but the actual code in git doesn't reflect the change.14:36
*** GuyElpotato has joined #automotive14:36
dl9pf??? wt* ?14:36
dl9pfcan you point to a changeset ?14:37
dl9pfkhilman: which changeset ?14:59
*** khouloud has joined #automotive15:00
khilmanhttps://gerrit.automotivelinux.org/gerrit/#/c/21062/15:09
khilmandl9pf: ^^^15:10
dl9pfyes, I see it.15:14
*** kbroulik has quit IRC15:22
*** AlisonChaiken has joined #automotive15:29
*** GuyElpotato has quit IRC15:30
*** AlisonChaiken has quit IRC15:37
*** leon-anavi has quit IRC15:47
dl9pfgerrit was rebooted. please report any issues.16:04
*** khouloud has quit IRC16:04
*** nayfe has quit IRC16:05
OutBackDingomoving on from PI3B+ so i guess ... no docs on adding our own BSP for our boards.... can i treat it like yocto as we have a BSD for yocto built for our board / CPU16:17
*** jobol has quit IRC16:48
furyOutBackDingo: same revision here, i'm stumped16:54
furyit should be fairly similar to yocto to set up a new board - see the other AGL BSPs in meta-agl/meta-agl-bsp16:55
furyOutBackDingo: if you haven't already, go ahead and put an issue up about it on JIRA - it might affect others as well16:56
*** psnsilva has quit IRC17:33
dl9pfOutBackDingo: a) you need a yocto layer compatible with yocto v2.6 'thud'19:40
dl9pfb) you need a template file (check meta-agl/templates/machines/19:40
dl9pfc) any adaptation/shim specific to your bsp and agl can go into meta-agl-bsp/meta-yourlayer19:41
dl9pfnote to b)  the template file can even be in your layer19:42
dl9pfjust match the folder structure19:43
*** khem has quit IRC19:44
*** khem has joined #automotive19:53
*** gkiagia has quit IRC21:39
*** fury has quit IRC21:39
*** paulbarker has quit IRC21:39
*** khilman has quit IRC21:43
*** OutBackDingo has quit IRC21:53
*** OutBackDingo has joined #automotive21:53
*** fury has joined #automotive22:07
*** paulbarker has joined #automotive22:07
*** khilman has joined #automotive22:08
*** OutBackDingo has quit IRC23:16
*** OutBackDingo has joined #automotive23:18
*** th3m1s has joined #automotive23:19
*** AlisonChaiken has joined #automotive23:31
*** AlisonChaiken has quit IRC23:42

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!