Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Shafqat Abbas <shafqat.abbas@skyelectric.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Information Required for Buildroot Image Issue
Date: Wed, 20 Mar 2024 16:46:59 +0100	[thread overview]
Message-ID: <20240320164659.08cd8673@gmx.net> (raw)
In-Reply-To: <CAL5xJooTe=qF8ngXTP45Uge0=ck546OnEzr2EaH4Qq5wrEj7rw@mail.gmail.com>

Hello Shafqat,

please keep buildroot@buildroot.org in CC...

On Wed, 20 Mar 2024 10:48:18 +0500, Shafqat Abbas <shafqat.abbas@skyelectric.com> wrote:

> Hi Peter,
> 
> I tried setting /dev management (Dynamic using devtmpfs + eudev), but it
> did not work. I am still facing the same issue. The USB keyboard is not
> working. Is there anything else that we need to set beside
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y?

Not that I am aware of (besides disconnect micro USB port (J11 USB slave)
you connected for flashing as described in the bug report), did you do a
full re-build of the whole system? Do you have a serial console attached
for further debugging?

Regards,
Peter

> 
> Regards.
> 
> Regards,
> *SHAFQAT ABBAS*
> Cybersecurity Engineer
> SkyElectric Inc.
> 
> 
> On Wed, Mar 20, 2024 at 3:27 AM Peter Seiderer <ps.report@gmx.net> wrote:
> 
> > On Tue, 19 Mar 2024 14:18:23 +0500, Shafqat Abbas <  
> > shafqat.abbas@skyelectric.com> wrote:  
> >  
> > > Hi,
> > >
> > > I hope you are doing well. I have been trying to compile the Linux OS for
> > > Raspberry Pi 4 (Compute Module / CM4) using buildroot. I have tried all  
> > the  
> > > default configurations available for raspberry pi systems. After writing
> > > the image to the pi, the system boots up properly, however, it does not
> > > read input from the keyboard. I am facing this issue on all builds. I  
> > have  
> > > also tried changing the board but that also resulted in the same issue.
> > >
> > > I am using the following steps to generate builds:
> > >
> > > 1. ```make raspberrypi_defconfig```
> > > 2. ```make```
> > >
> > > I have used this method for compiling builds for all defconfigs,  
> > including  
> > > the following:
> > > 1. Build for *Raspberry Pi*
> > > 2. Build for *Raspberry Pi 4*
> > > 3. Build for *Raspberry* *Pi 4 (64 bit)*
> > > 4. Build for *Raspberry Pi CM4 IO*
> > > 5. Build for *Raspberry Pi CM4 IO (64 bit)*
> > >
> > > The keyboard does not work at all. Even the lights do not work, which  
> > shows  
> > > that the keyboard is not connected, however the same keyboard works fine  
> > on  
> > > other systems.
> > >
> > > So, the assumption is that the keyboard is fine, the board is fine, the  
> > RPi  
> > > is fine, and the issue lies in the build compiled by buildroot.
> > >
> > > I kindly request the community to help me sort out this issue. Thanks a  
> > lot
> >
> > See 'Bug 15910 - USB keyboard is not working by default
> > "raspberrypicm4io_64_defconfig"'
> > ([1]) for the same problem and different solutions...
> >
> > Regards,
> > Peter
> >
> > [1] https://bugs.busybox.net/show_bug.cgi?id=15910
> >  

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-03-20 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  9:18 [Buildroot] Information Required for Buildroot Image Issue Shafqat Abbas
2024-03-19 22:27 ` Peter Seiderer via buildroot
     [not found]   ` <CAL5xJooTe=qF8ngXTP45Uge0=ck546OnEzr2EaH4Qq5wrEj7rw@mail.gmail.com>
2024-03-20 15:46     ` Peter Seiderer via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240320164659.08cd8673@gmx.net \
    --to=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    --cc=shafqat.abbas@skyelectric.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox