[beagleboard] Re: User LEDs control

[Joshua Park]

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 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 subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/acfff9b2-a632-47a7-a4f0-29991e4475c5n%40googlegroups.com.

[beagleboard] User LEDs control

[Joshua Park]

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 subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4488829d-82cf-4774-b538-345882e9fa19n%40googlegroups.com.

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

[Joshua Park]

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. To 
> >build one do I just create a DTS file in the /opt/source/dtb-5.4-ti/src 
> and 
> >run *make /src//custom.dts? *Also to install the DTB for u-boot, I 
> >need to move the file into /boot/dtbs/$(uname -r) for debian as stated 
> here 
> >
> https://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0#u-boot_dtb_search_order
> > right?
> You are now beyond what I can find by Google and on-board file
> searches.
>
>
> -- 
> Dennis L Bieber
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5b595fcd-21e7-4c90-b05e-c5fb13bf5718n%40googlegroups.com.

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

[Joshua Park]

Ok, so what I think I need to do is make a custom DTB for my board. To 
build one do I just create a DTS file in the /opt/source/dtb-5.4-ti/src and 
run *make /src//custom.dts? *Also to install the DTB for u-boot, I 
need to move the file into /boot/dtbs/$(uname -r) for debian as stated here 
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,
> >
> >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 
> >file?
>
> You don't... It doesn't exist as a file, just a virtual name in the
> file system. When you read it, the OS generates the data it gives to you.
> https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
>
> I suspect you need to edit the appropriate device tree source file,
> compile it into a DTB, and install that DTB where ever u-boot is looking...
>
>
> debian@beaglebone:~$ cat /proc/device-tree/model
> TI AM335x BeagleBone Blackdebian@beaglebone:~$
> debian@beaglebone:~$ grep -i "TI AM335x BeagleBone Black"
> /opt/source/dtb-4.19-ti/src/arm/*.dts
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-audio.dts: model = "TI
> AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-bbb-exp-c.dts: model = "TI
> AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-bbb-exp-r.dts: model = "TI
> AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-bbbmini.dts: model = "TI
> AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack.dts: model = "TI AM335x
> BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-roboticscape.dts: model =
> "TI AM335x BeagleBone Black RoboticsCape";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-uboot.dts: model = "TI
> AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-uboot-univ.dts: model =
> "TI AM335x BeagleBone Black";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-wireless.dts: model = "TI
> AM335x BeagleBone Black Wireless";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-wireless-roboticscape.dts:
> model = "TI AM335x BeagleBone Black Wireless RoboticsCape";
> /opt/source/dtb-4.19-ti/src/arm/am335x-boneblack-wl1835mod.dts: model = "TI
> AM335x BeagleBone Black";
> debian@beaglebone:~$
>
>
> -- 
> Dennis L Bieber
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/518a9b15-6ec4-49d4-98b1-2ad0cf8ac91cn%40googlegroups.com.

[beagleboard] Device-tree/model file changes

[Joshua Park]

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 
file?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/31a9ea31-e8dc-4439-933e-49fa0847d99cn%40googlegroups.com.

[beagleboard] Beagleboard listen address

[Joshua Park]

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 
rerunning each of those scripts but the changes do not occur until I reboot 
the system. How would I go about changing the listen address without 
rebooting the board?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1571ec70-5384-4ea3-a646-62b01f3f03a8n%40googlegroups.com.

[beagleboard] Pocket Beagle Image Repo

[Joshua Park]

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 version 
used in the pocket beagle image. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1a0b59f4-64c3-429d-9218-5d215dfb66f8n%40googlegroups.com.

Re: [beagleboard] USB Network Gadget Configuration

[Joshua Park]

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 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 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 establish the network over USB (assigning the host 
>> computer 192.168.7.1 and itself 192.168.7.2) remains the same with the 
>> image that I built. However, the USB network does not work out of the box 
>> for the image that I built. Can anyone point me in the right direction on 
>> what to configure in order to get the USB network working?
>>
>> In the last year there has been a lot of churn in the boot script used
>> to enable the usb-gadget configuration..
>>
>> For a board with normal ethernet, running:
>>
>> git pull under /opt/scripts/ should be enough.. but for PocketBeagle..
>>
>> HEre's a newer version of the RootFileSystem, just haven't pushed it
>> to the eewiki yet..
>>
>>
>> https://rcn-ee.net/rootfs/eewiki/minfs/debian-10.5-minimal-armhf-2020-08-02.tar.xz
>>
>> Regards,
>>
>> -- 
>> Robert Nelson
>> https://rcn-ee.com/
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/73d35320-16fb-4494-aea4-63dc0d074e6dn%40googlegroups.com.

Re: [beagleboard] USB Network Gadget Configuration

[Joshua Park]

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 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 establish the network over USB (assigning the host 
> computer 192.168.7.1 and itself 192.168.7.2) remains the same with the 
> image that I built. However, the USB network does not work out of the box 
> for the image that I built. Can anyone point me in the right direction on 
> what to configure in order to get the USB network working?
>
> In the last year there has been a lot of churn in the boot script used
> to enable the usb-gadget configuration..
>
> For a board with normal ethernet, running:
>
> git pull under /opt/scripts/ should be enough.. but for PocketBeagle..
>
> HEre's a newer version of the RootFileSystem, just haven't pushed it
> to the eewiki yet..
>
>
> https://rcn-ee.net/rootfs/eewiki/minfs/debian-10.5-minimal-armhf-2020-08-02.tar.xz
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e7a8700c-b736-4c34-a799-11def753195an%40googlegroups.com.

[beagleboard] USB Network Gadget Configuration

[Joshua Park]

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 establish the 
network over USB (assigning the host computer 192.168.7.1 and itself 
192.168.7.2) remains the same with the image that I built. However, the USB 
network does not work out of the box for the image that I built. Can anyone 
point me in the right direction on what to configure in order to get the 
USB network working?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/eeb19716-52fa-4e39-bc8e-2c8dbb4dde26n%40googlegroups.com.

Re: [beagleboard] Blank Board ID U-boot

[Joshua Park]

Thanks for your help

On Thursday, August 13, 2020 at 1:14:02 PM UTC-4 jimf...@gmail.com wrote:

> I'm off work today so I can't say exactly what versions I was using, but I 
> recall following the instructions verbatim and everything worked perfectly.
>
> I suppose if your modifications to the u-boot source were bad enough, you 
> could cause boot to fail. If I recall correctly, I started by allowing the 
> blank eeprom case to follow the black boot path. That seemed easiest to get 
> started and I think it just added an OR to an if statement.
>
> Figuring out 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 using u-boot version 2018.03rc1 when you made it work? That is 
>> the only thing that I had to change when following pocket beagle image 
>> tutorial <https://www.digikey.com/eewiki/display/linuxonarm/PocketBeagle> 
>> since the 0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch 
>> provided in the blank board ID method is written for that version. In case 
>> I made a mistake somewhere I will go back and try again.
>>
>> On Thursday, August 13, 2020 at 12:31:48 PM UTC-4 jimf...@gmail.com 
>> wrote:
>>
>>> It should work on an original pocket beagle. Like I told Sam Park in a 
>>> separate thread, you basically must have a serial debug adapter connected 
>>> to the device to debug u-boot issues.
>>>
>>> I can say that I have followed rcn's instructions for building and 
>>> installing u-boot and followed octavo's directions for modifying a board 
>>> with a blank eeprom, 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 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 found out that the image for some reason does not 
>>>> boot on the original Pocket Beagle. Why is this the case? As far as I 
>>>> know, 
>>>> utilizing a blank board ID is not the recommended way to boot however I 
>>>> don't see why it shouldn't boot with the original Pocket Beagle. Thanks.
>>>>
>>>> -- 
>>>> For more options, visit http://beagleboard.org/discuss
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "BeagleBoard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to beagleboard...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/4eeffa58-5a80-429a-a9e0-bf32f1800182n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/4eeffa58-5a80-429a-a9e0-bf32f1800182n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/01981b6b-6832-4226-b0eb-48ce47396988n%40googlegroups.com.

Re: [beagleboard] Blank Board ID U-boot

[Joshua Park]

Were you using u-boot version 2018.03rc1 when you made it work? That is the 
only thing that I had to change when following pocket beagle image tutorial 
<https://www.digikey.com/eewiki/display/linuxonarm/PocketBeagle> since the 
0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch provided in 
the blank board ID method is written for that version. In case I made a 
mistake somewhere I will go back and try again.

On Thursday, August 13, 2020 at 12:31:48 PM UTC-4 jimf...@gmail.com wrote:

> It should work on an original pocket beagle. Like I told Sam Park in a 
> separate thread, you basically must have a serial debug adapter connected 
> to the device to debug u-boot issues.
>
> I can say that I have followed rcn's instructions for building and 
> installing u-boot and followed octavo's directions for modifying a board 
> with a blank eeprom, 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 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 found out that the image for some reason does not boot on 
>> the original Pocket Beagle. Why is this the case? As far as I know, 
>> utilizing a blank board ID is not the recommended way to boot however I 
>> don't see why it shouldn't boot with the original Pocket Beagle. Thanks.
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4eeffa58-5a80-429a-a9e0-bf32f1800182n%40googlegroups.com.

[beagleboard] Blank Board ID U-boot

[Joshua Park]

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 found out that the image for some reason does not boot on 
the original Pocket Beagle. Why is this the case? As far as I know, 
utilizing a blank board ID is not the recommended way to boot however I 
don't see why it shouldn't boot with the original Pocket Beagle. Thanks.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1715f20d-48b4-4a31-b330-b950ccad2059n%40googlegroups.com.

[beagleboard] U-Boot patches for 2018.03rc1

[Joshua Park]

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 because the first two patches in the guide must be applied first and 
they do not work either because they are made for the wrong code version. I 
would like to know if newer versions for the first two patches 
(0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch and 
0002-U-Boot-BeagleBone-Cape-Manager.patch) exist for u-boot version 
2018.03rc1. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dda193d1-202f-430b-bc13-6ef2f2291d7bn%40googlegroups.com.