[beagleboard] Re: User LEDs control

Also, I figure that I process is controlling the blinking of user LED 1 since that is the only one I cannot change. Can anyone tell me what this process is and if I can stop it from controlling LED 1? On Sunday, October 11, 2020 at 3:01:06 PM UTC-4 Joshua Park wrote: > Hi all, > > I

[beagleboard] User LEDs control

Hi all, I am trying to change the user LEDs but I am unable to make permanent changes to the files in */sys/devices/platform/leds/leds*. Can someone help me out? Thanks in advance. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are

[beagleboard] Re: Device-tree/model file changes

Ok, thanks for your help. On Thursday, October 1, 2020 at 1:45:52 PM UTC-4 Dennis Bieber wrote: > On Thu, 1 Oct 2020 07:25:50 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Joshua Park > wrote: > > >Ok, so what I think I need to do is make a custom DTB for my board. T

[beagleboard] Re: Device-tree/model file changes

https://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0#u-boot_dtb_search_order right? On Thursday, October 1, 2020 at 1:54:53 AM UTC-4 Dennis Bieber wrote: > On Wed, 30 Sep 2020 17:22:54 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Joshua Park > wrote: > > >Hi all,

[beagleboard] Device-tree/model file changes

Hi all, I'm trying to edit the /proc/device-tree/model file in the debian-10.3-iot-armhf-2020-04-06 version file system. I have tried as root and changed the permissions of the file and its parent directories but the file remains unwritable. Can anyone tell me how I am supposed to edit this

[beagleboard] Beagleboard listen address

Hi all, I'm currently trying to change the network interface usb0's listen-address on the pocket beagle image without rebooting the board. I have tried editing the values for USB0-ADDRESS in /etc/default/bb-boot, /opt/scripts/boot/default/bb-boot, and /usr/bin/bb_dnsmasq_config.sh and

[beagleboard] Pocket Beagle Image Repo

Hello all, Does anyone know if a downloadable repository for the beagleboard.org's pocket beagle image (AM3358 Debian 10.3 2020-04-06 4GB SD IoT) exists? I've looked through the eewiki but I can't find the same

Re: [beagleboard] USB Network Gadget Configuration

I'm pretty sure the problem is that the scripts in /opt/scripts/boot are not running at startup. How does the pocket beagle image run those scripts at boot? I don't see a /etc/rc.local file. On Friday, August 14, 2020 at 2:02:43 PM UTC-4 Joshua Park wrote: > Should the image bu

Re: [beagleboard] USB Network Gadget Configuration

Should the image built with the newer RootFileSystem have the USB network working out of the box? On Friday, August 14, 2020 at 1:26:38 PM UTC-4 RobertCNelson wrote: > On Fri, Aug 14, 2020 at 12:19 PM Joshua Park wrote: > > > > Hello everyone, > > > > I've built a

[beagleboard] USB Network Gadget Configuration

Hello everyone, I've built a pocket beagle Debian image following this tutorial and I have confirmed that software that is preinstalled in the Bone Debian images for pocket beagle that

Re: [beagleboard] Blank Board ID U-boot

ut what's happening without a serial debug port is feeling > around blind. If you're not getting paid for it, it's not so bad, but it > wastes a lot of time. No way could I do that at work. > > Good luck. > > On Thu, Aug 13, 2020, 1:07 PM Joshua Park wrote: > >> Were you

Re: [beagleboard] Blank Board ID U-boot

and things worked perfectly, for me. > > Good luck! > > On Thu, Aug 13, 2020, 11:12 AM Joshua Park wrote: > >> >> Hi all, >> >> I'm currently working on a project involving a custom SBC based off the >> Pocket Beagle. I'm in the process of building a ima

[beagleboard] Blank Board ID U-boot

Hi all, I'm currently working on a project involving a custom SBC based off the Pocket Beagle. I'm in the process of building a image for it and I am trying to utilize a blank board ID mentioned here: https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/. However upon testing, I

[beagleboard] U-Boot patches for 2018.03rc1

I am currently attempting to make u-boot recognize a blank board ID as described this guide (section 4.2). The problem is that the 0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch does not work