Hi Christian, I don't think the clock is the error here (mostly a red-herring). If you look at the recipe that Emily is excluding (init-clock) -- it's an update-rc.d recipe meaning it's installing itself to run on linux boot -- and it's a python script.
Strangely, including it seems to cause the board to not boot, which doesn't seem like a trivial problem. Cheers, Giordon On Wed, Mar 20, 2019 at 10:26 AM Christian Dreher <cdre...@prophesee.ai> wrote: > For the clock tree configuration, in my projects, I use the Vivado > configuration tool, , and then generates the psu_init_gpl files. It's > static, but it fits my needs and I don't know if there is any other > solution (it's the only one advertised in the Xilinx documentation I read). > Actually, in my design, SDIO0 and SDIO1 comes from either VPLL, IOPLL or > RPLL, and vivado offers me no other source than PS_REF_CLK for those PLL, > this may be a dead end. > > Regarding the 5345, the easiest way should be to reset it through i2c and > ton read its registers value after reset. All registers and reset > procedures should be described in the chip datasheet. Also in some > organization, the easiest way to know what changes were made on the board > is just to ask around (but it doesn't work everywhere, and may be > unreliable). > ------------------------------ > *From:* Emily S <easmith5...@gmail.com> > *Sent:* Tuesday, March 19, 2019 17:26 > *To:* Christian Dreher > *Cc:* Mike Looijmans; meta-xilinx@yoctoproject.org > > *Subject:* Re: [meta-xilinx] devtmpfs: error mounting -2 > Hi Christian - > > Thanks for your response! That's interesting, is there a way to check if > we're relying on a clock for the SDIO interface? The problems I was seeing > would be explained by erroneous reads on the SD card, but I'd be surprised > if the SDIO relied on a clock, as everything does seem to function okay > when I remove the recipe entirely. It might be also good to check if a > configuration was written in the non-volatile memory, but again, not sure > how to check that. > > Thanks! > Emily > > On Mon, Mar 18, 2019 at 12:07 PM Christian Dreher <cdre...@prophesee.ai> > wrote: > > Hi, > > I quickly looked at your layer, it seems to setup a Si5345. If you rely on > one of its clocks for your SDIO interface, an erroneous configuration, > either in the Si5345 init code or in the clock tree for the zynq may result > on erroneous reads on the SD card. I had the same symptoms in a totally > different project (with a SoC from a different vendor) when a driver was > unable to set the correct speed for the SDIO interface. > > However, it's strange that removing init-clock improve the situation: if > your SDIO interface depends on a clock provided by the Si5345, it should > not work at all without configuring the Si5345, unless a configuration was > written in the Si5345 non-volatile memory. > > Anyway, you should look for configuration changes in your PS clock > configuration. > > I hope this may help > ------------------------------ > *From:* meta-xilinx-boun...@yoctoproject.org < > meta-xilinx-boun...@yoctoproject.org> on behalf of Emily S < > easmith5...@gmail.com> > *Sent:* Monday, March 18, 2019 16:43 > *To:* Mike Looijmans > *Cc:* meta-xilinx@yoctoproject.org > *Subject:* Re: [meta-xilinx] devtmpfs: error mounting -2 > > Hi Mike - > > Thanks for the response. When I removed the init-clock recipe from our > custom layer ( > https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/init/init-clock_1.0.0.bb) > the board boots fine now. Any thoughts on why this recipe causes problems? > It seemed to work fine a few months ago. > > Best, > Emily > > On Fri, Mar 15, 2019 at 6:14 AM Mike Looijmans <mike.looijm...@topic.nl> > wrote: > > since error "2" is this: > > #define ENOENT 2 /* No such file or directory */ > > my guess would be that your rootfs does not actually contain a "/dev" > directory for the filesystem to mount on. > > > On 12-03-19 20:38, Emily S wrote: > > Hi All - > > > > I'm using Yocto version rocko with a custom layer to run on the Zynq+ > SoC on a > > custom board. When trying to boot I'm getting an error like: > > > > [ 4.178864] devtmpfs: error mounting -2 > > > > in the boot output. Even after rolling back to a previous working > version I > > still get this error in the boot output. After this error, the boot > process > > seems to stop, and I am directly given a terminal input, but no login, > or > > anything. The /dev and /proc folders seem to be missing as does > specifically > > /etc/network/ among others. > > > > I'm booting from an SD card and flashing it using a wic image made with > the > > "sdimage-bootpart.wks" from yocto. This method has worked fine before > now. > > > > Are there obvious things I should check to make sure devtmpfs can be > mounted > > properly? I have not messed with bootargs or anything since the working > > version of the OS, so I'm not sure why I am suddenly seeing this error. > > > > A comparison output from the working OS and the bad OS can be seen > below. Any > > ideas are greatly appreciated! > > > > Thanks, > > Emily > > > > *Bad OS: * > > [ 4.125754] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to > feature > > incompatibilities > > [ 4.163579] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data > mode. > > Opts: (null) > > [ 4.171613] VFS: Mounted root (ext4 filesystem) on device 179:2. > > [ 4.178864] devtmpfs: error mounting -2 > > [ 4.182766] Freeing unused kernel memory: 640K (ffffffc000d20000 - > > ffffffc000dc0000) > > /bin/sh: can't access tty; job control turned off > > / # > > > > *Working OS: * > > [ 4.089697] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to > feature > > incompatibilities > > [ 5.324662] EXT4-fs (mmcblk0p2): recovery complete > > [ 5.404047] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data > mode. > > Opts: (null) > > [ 5.412083] VFS: Mounted root (ext4 filesystem) on device 179:2. > > [ 5.418084] devtmpfs: mounted > > [ 5.421106] Freeing unused kernel memory: 512K (ffffffc000c10000 - > > ffffffc000c90000) > > > > ... (boot continues) > > > > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx > -- Giordon Stark
-- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
