Hello Laurent

I am building for qemuriscv64

Command :-
MACHINE=qemuriscv64 bitbake core-image-full-cmdline


Thank you.

Regards
Vaibhav Vivek Deshpande


On Thu, Oct 20, 2022 at 11:00 PM Laurent Gauthier <
[email protected]> wrote:

> Hi Vaibhav,
>
> Out of curiosity which image did you build?
>
> Kind regards, Laurent.
>
> On Thu, Oct 20, 2022 at 7:07 PM Vaibhav Deshpande
> <[email protected]> wrote:
> >
> > Helo
> >
> > I have added systemd in rootfs by adding IMAGE_INSTALL = " systemd" in
> local.conf and the issue solved
> > is this required for the latest yocto version (kirkstone)?
> >
> >
> > Thank you.
> >
> > Regards
> > Vaibhav Vivek Deshpande
> >
> >
> > On Mon, Oct 17, 2022 at 1:28 AM Zoran Stojsavljevic <
> [email protected]> wrote:
> >>
> >> Interesting... Looking into the log massage itself!
> >>
> >> > [    0.000000] Kernel command line: root=/dev/vda2 rootwait
> console=ttyS0 earlycon=uart8250,mmio,0x10000000
> >>
> >> Command line does not specify baud rate... Usually by default it is
> >> 115200. Just a kludge.
> >>
> >> Then:
> >>
> >> > [    0.000000] earlycon: uart8250 at MMIO 0x0000000010000000 (options
> '')
> >> > [    0.000000] printk: bootconsole [uart8250] enabled
> >>
> >> bootconsole enabled, seems correct.
> >>
> >> Then:
> >>
> >> > [    1.628806] Serial: 8250/16550 driver, 4 ports, IRQ sharing
> disabled
> >> > [    1.648238] printk: console [ttyS0] disabled
> >> > [    1.652252] 10000000.uart: ttyS0 at MMIO 0x10000000 (irq = 166,
> base_baud = 230400) is a 16550A
> >> > [    1.656816] printk: console [ttyS0] enabled
> >> > [    1.656816] printk: console [ttyS0] enabled
> >> > [    1.657728] printk: bootconsole [uart8250] disabled
> >> > [    1.657728] printk: bootconsole [uart8250] disabled
> >>
> >> From what we see that the base baud rate is 230400 (?), everything
> >> else is, seems, correct.
> >>
> >> So, three things, which came adhoc to my mind:
> >> [1] Please, check the baud rate;
> >> [2] Please, check to which group /dev/ttyS0 belongs (root dialout)?
> >> [3] The terminal should be interactive, but no way to check this (from
> >> the logs)???
> >>
> >> My two cent worth answer,
> >> Zee
> >> _______
> >>
> >> On Sun, Oct 16, 2022 at 8:32 PM Vaibhav Deshpande
> >> <[email protected]> wrote:
> >> >
> >> > Hello
> >> >
> >> > I am trying to build a yocto image from the kirkstone branch (
> https://github.com/openembedded/openembedded-core/tree/kirkstone) build
> gets successful but at the time of linux booting I am getting below error.
> >>
> >> ...[snap]...
> >
> >
> > 
> >
>
>
> --
> Laurent Gauthier
> Embedded Linux Systems & Software
> Phone: +33 630 483 429
> https://soccasys.com
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58389): https://lists.yoctoproject.org/g/yocto/message/58389
Mute This Topic: https://lists.yoctoproject.org/mt/94368916/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to