Re: [beagleboard] Re: Connecting Two BBBWs to One Another and Using One Script?

[set_]

Hello Jon,

Seth here. I am dealing w/ this now:  
https://websockets.readthedocs.io/en/stable/intro.html . It seems this may 
be easier on me as they have handled most of everything behind the scenes.

Also, I can chat w/ the two boards now and get input/output on the 
terminal. I think my first step would be to set up a chat and work my way 
to a LED and then to motors.

Seth

P.S. I will try to keep this page open to keep up w/ ideas relative to 
websockets and Python. 

On Friday, August 21, 2020 at 12:03:26 AM UTC-5 jonn...@gmail.com wrote:

> I've used both a BBB and a RasPi for the Mosquitto server.  It is a 
> lightweight server so it should not be too taxing on a system. 
>
> Cheers,
>
> Jon
>
> On Thu, Aug 20, 2020 at 8:17 PM set_  wrote:
>
>> Hello,
>>
>> I got the Mosquitto and paho-mqtt testing on my BBBW and BBGW. I can run 
>> a broker on each of them so far. I can also run some extra scripts in 
>> python to make them "almost work." 
>>
>> ...
>>
>> Should I be using the BBGW/BBBW as a broker or should I use a larger 
>> computer as the broker?
>>
>> Seth
>>
>> P.S. I started to use this idea w/ websockets too.
>>
>> On Sunday, August 16, 2020 at 1:45:16 PM UTC-5 jonn...@gmail.com wrote:
>>
>>> You could use something like MQTT where you run the Mosquitto MQTT 
>>> server on one of the BBBW and then publish and subscribe to shared topics 
>>> between the two.  I believe Node-RED might be another option.
>>>
>>>
>>>
>>> On Sun, Aug 16, 2020 at 8:56 AM Dennis Lee Bieber  
>>> wrote:
>>>
 On Sat, 15 Aug 2020 20:47:51 -0700 (PDT), in
 gmane.comp.hardware.beagleboard.user set_
  wrote:

 >
 >I mean, I can test UART connections b/t the two boards. This is not my 
 >concern. I am trying to use one script to control both boards. I mean, 
 I 
 >can break them up and try that setup too. 
 >
 >I would rather have _ work to make one script compiled 
 communicate 
 >my interests to the boards at my disposal. 
 >

 I believe you are going to have to define some sort of 
 distributed
 communication protocol, and run some sort of command interpreter on the
 second board. The first board would then have to format and send 
 commands
 over the link to the second board for execution. The command definitions
 will have to cover all operation categories you want to perform on the
 second board (set motor speed, or whatever it is supposed to do), and
 probably include return values too.

 Depending upon how you create this protocol library, it may be 
 possible
 to, say, run the command processor on each board using TCP/IP and 
 listening
 on "commandport", and your master script would open sockets to
 "localhost:commandport" and "otherhost:commandport". This way, you use 
 the
 same command sequences for both boards (and can expand if needed --
 "anotherhost:commandport").

 Your top-level control script only needs to know the IP/port 
 for each
 controller board. You run the same processor code as a server on each
 board.



 -- 
 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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/beagleboard/36lijf9tr63qecfjj9j982oom5snk9apqu%404ax.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...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/c7c8ea82-41d4-4244-bb08-7f13fb8d4742n%40googlegroups.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/a4f07de4-2183-4c65-8cf2-c69e7d2cd215n%40googlegroups.com.

[beagleboard] Re: Latest Image - Summer 2020 Release - RC1

[Robert Nelson]

I should mention the location for "combined" overlays is this repo and branch:

https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays

Here is the current list of tested overlays:

https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays

Overlays can now be loaded via:

uboot_overlay_addr0=.dtbo

vs:

uboot_overlay_addr0=/lib/firmware/.dtbo

As the updated u-boot will now search the two locations:

/boot/dtbs//overlays/
and
/lib/firmware/

yet still know how to load the old way..

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/CAOCHtYjYy5_ezbC%3DX2JUxCGdbun6%3DbffppjogW2o3%2B_c9RidcA%40mail.gmail.com.

[beagleboard] Latest Image - Summer 2020 Release - RC1

[Robert Nelson]

Hi Everyone!

It's that time, things got way late with Covid/etc, plus we've merged
a lot of GSOC 2020 and MLH 2020 code into this release!

For the Summer 2020 release, this will be the last time we publish a
Debian 9 (Stretch) Build, that version is pretty much "oldstable" at
Debian and is not getting many updates..

Both Stretch and Buster have 3 base variants:

Console
IoT
LXQt

In level of installed package complexity..

For BBAI users, there are special IoT and LXQt variants of the TIDL,
just note these all still use the older v4.14.x-ti kernel..  I'm still
working on v4.19.x-ti support..

Otherwise, Stretch = v4.14.x-ti and Buster = v4.19.x-ti

We had some fun getting v5.4.x-ti ready, but just ran out of time.

But BEST of all, the v4.19.x-ti has a new overlay rewrite from our
2020 GSOC student that allows a "complex" overlay to be used on both
the AM335x and AM57xx devices.

I'm still fighting some fun AM57xx u-boot i2c read errors, but on a
clean startup, the BBAI will read the i2c eeprom and try to load the
proper overlay..

https://elinux.org/Beagleboard:Latest-images-testing#Latest_Images_Testing

So go please test! real release in a couple weeks..

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/CAOCHtYiC%3Db84TdiA-kMmsZ%2B23%3DuxVqHwcMx9AVDi_-iC8dP%3DzA%40mail.gmail.com.

[beagleboard] Re: Can't control LEDs on BBB from terminal

[Dennis Lee Bieber]

On Fri, 21 Aug 2020 07:41:18 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko
 wrote:

>Here is kernel:
>4.14.108-ti-r119
>
>But it doesn't boot anymore !
>
>After update and installing bb-customization I get this:

Considering you also have a thread about not getting a custom u-Boot to
work, I no longer have any idea of what combination of stuff you may have
on the board.

At this point I'd start with a fresh SD card (8GB or more) with a
recent GOOD OS image (yes, there are newer images in the testing directory,
but I'm trying to minimize unknowns)
https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz

Run the script to resize the image for the full SD card

Boot the SD card, and run "sudo apt update" / "sudo apt upgrade" (Since
April, the repository is up to Debian 10.5, so this may entail quite a few
packages -- hence the recommendation to use an 8GB card).

When you've verified that this card is functioning properly, you might
convert it to a flasher image (last line in /boot/uEnv.txt); reboot, and
let it flash the eMMC with a good set-up. When done, remove the SD card (if
you leave it in and reboot, it will just repeat the flashing operation).
Reboot, and verify the eMMC is working as desired.

When booting on eMMC, you can /then/ insert the SD card, mount it into
the file system, and modify the /boot/uEnv.txt to disable the flasher
mode). That will give you a working SD card for development.

Don't write anything to the eMMC until you've debugged it from SD card.


-- 
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/3lpvjflvbjfp13mvjot2vrt733brdpop3e%404ax.com.

Re: [beagleboard] Re: Cannot see U-Boot# prompt in terminal

[Robert Nelson]

On Fri, Aug 21, 2020 at 9:29 AM Pavel Yermolenko  wrote:
>
> Here is my sd-card:
>
> debian@beaglebone:~$ lsblk
> NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> mmcblk1  179:00  3.6G  0 disk
> └─mmcblk1p1  179:10  3.6G  0 part /
> mmcblk1boot0 179:802M  1 disk
> mmcblk1boot1 179:16   02M  1 disk
> mmcblk1rpmb  179:24   0  512K  0 disk
> mmcblk0  179:32   0 14.9G  0 disk
> ├─mmcblk0p1  179:33   0   64M  0 part
> └─mmcblk0p2  179:34   01G  0 part
>
> I executed script without modifs:
> debian@beaglebone:/opt/scripts/tools$ sudo ./generate_extlinux.sh
> [sudo] password for debian:
> debian@beaglebone:/opt/scripts/tools$
>
> But nothing changed on sd-card.
> I still see u-boot.img and MLO in /boot.

Shakes head, i haven't tested for the old "dual partition" setup in
years.. I killed it back in 2014 and moved to a single ext4 partition
ever since.

Sorry, it's just never tested..

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/CAOCHtYiSQkXGnVXaVXXSuRSs0AfCYrf%2BzbM%3D0W0gLW5Y37krzg%40mail.gmail.com.

Re: [beagleboard] Re: Can't control LEDs on BBB from terminal

[Robert Nelson]

On Fri, Aug 21, 2020 at 9:41 AM Pavel Yermolenko  wrote:
>
> Here is kernel:
> 4.14.108-ti-r119
>
> But it doesn't boot anymore !
>
> After update and installing bb-customization I get this:
> Starting kernel ...
>
> [0.000771] timer_probe: no matching timers found
> [0.610313] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
> [0.850039] omap_voltage_late_init: Voltage driver support not added
> [0.857068] PM: Cannot get wkup_m3_ipc handle
> [1.163793] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: no source 
> widget found for Playback
> [1.172667] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: Failed to add 
> route Playback -> direct -> TX
> [1.187598] Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
> [1.195919] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.108-ti-r119 #1
> [1.202735] Hardware name: Generic AM33XX (Flattened Device Tree)
> [1.208902] [] (unwind_backtrace) from [] 
> (show_stack+0x20/0x24)
> [1.216694] [] (show_stack) from [] 
> (dump_stack+0x80/0x94)
> [1.223958] [] (dump_stack) from [] (panic+0x100/0x284)
> [1.230959] [] (panic) from [] 
> (mount_block_root+0x1b8/0x2a4)
> [1.238481] [] (mount_block_root) from [] 
> (mount_root+0x140/0x15c)
> [1.246436] [] (mount_root) from [] 
> (prepare_namespace+0x160/0x1a8)
> [1.254479] [] (prepare_namespace) from [] 
> (kernel_init_freeable+0x25c/0x270)
> [1.263401] [] (kernel_init_freeable) from [] 
> (kernel_init+0x18/0x128)
> [1.271716] [] (kernel_init) from [] 
> (ret_from_fork+0x14/0x2c)
> [1.279347] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unknown-block(0,0)
> [2.047863] [drm] Cannot find any crtc or sizes

No, bb-customization is just a bunch of udev rules, that wouldn't do that..

https://github.com/rcn-ee/repos/tree/master/bb-customizations/suite/stretch/debian

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/CAOCHtYiVsQHnfnkBfg1qGKRWb3GzAFzxOt_TrSGDYBvziM6_nA%40mail.gmail.com.

[beagleboard] Re: Can't control LEDs on BBB from terminal

[Pavel Yermolenko]

Here is kernel:
4.14.108-ti-r119

But it doesn't boot anymore !

After update and installing bb-customization I get this:
Starting kernel ...

[0.000771] timer_probe: no matching timers found
[0.610313] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[0.850039] omap_voltage_late_init: Voltage driver support not added
[0.857068] PM: Cannot get wkup_m3_ipc handle
[1.163793] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: no source 
widget found for Playback
[1.172667] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: Failed to 
add route Playback -> direct -> TX
[1.187598] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[1.195919] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.108-ti-r119 #1
[1.202735] Hardware name: Generic AM33XX (Flattened Device Tree)
[1.208902] [] (unwind_backtrace) from [] 
(show_stack+0x20/0x24)
[1.216694] [] (show_stack) from [] 
(dump_stack+0x80/0x94)
[1.223958] [] (dump_stack) from [] 
(panic+0x100/0x284)
[1.230959] [] (panic) from [] 
(mount_block_root+0x1b8/0x2a4)
[1.238481] [] (mount_block_root) from [] 
(mount_root+0x140/0x15c)
[1.246436] [] (mount_root) from [] 
(prepare_namespace+0x160/0x1a8)
[1.254479] [] (prepare_namespace) from [] 
(kernel_init_freeable+0x25c/0x270)
[1.263401] [] (kernel_init_freeable) from [] 
(kernel_init+0x18/0x128)
[1.271716] [] (kernel_init) from [] 
(ret_from_fork+0x14/0x2c)
[1.279347] ---[ end Kernel panic - not syncing: VFS: Unable to mount 
root fs on unknown-block(0,0)
[2.047863] [drm] Cannot find any crtc or sizes


On Friday, August 21, 2020 at 4:24:59 PM UTC+2, Dennis Bieber wrote:
>
> On Fri, 21 Aug 2020 06:05:46 -0700 (PDT), in 
> gmane.comp.hardware.beagleboard.user Pavel Yermolenko 
> > wrote: 
>
> >Thanks Dennis, 
> > 
> >In my case there is no *gpio, *but *root* 2 times. 
> > 
>
> I'll repeat my previous question: How old is the OS image on that 
> device? 
>
> >debian@beaglebone:~$ ls -l /sys/class/leds/ 
> >total 0 
> >lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr0 -> 
> >../../devices/platform/leds/leds/beaglebone:green:usr0 
>
> That "Jan 1 2000" also alarms me, though I am quite sure no Beagle 
> images go back that far. At best I suspect you have no connection to an 
> NTP 
> server -- since my system shows a time stamp of yesterday, just before 
> noon 
> -- which was probably when I ran "sudo apt update" / "sudo apt upgrade -y" 
>
>
> -- 
> 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/25797d2f-a218-47cd-b0c5-e7fc40a23b92o%40googlegroups.com.

Re: [beagleboard] Re: Cannot see U-Boot# prompt in terminal

[Pavel Yermolenko]

Here is my sd-card:

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1  179:00  3.6G  0 disk 
└─mmcblk1p1  179:10  3.6G  0 part /
mmcblk1boot0 179:802M  1 disk 
mmcblk1boot1 179:16   02M  1 disk 
mmcblk1rpmb  179:24   0  512K  0 disk 
mmcblk0  179:32   0 14.9G  0 disk 
├─mmcblk0p1  179:33   0   64M  0 part 
└─mmcblk0p2  179:34   01G  0 part 

I executed script without modifs:
debian@beaglebone:/opt/scripts/tools$ sudo ./generate_extlinux.sh 
[sudo] password for debian: 
debian@beaglebone:/opt/scripts/tools$ 

But nothing changed on sd-card.
I still see *u-boot.img* and *MLO* in /boot.


On Friday, August 21, 2020 at 3:52:21 PM UTC+2, RobertCNelson wrote:
>
> On Fri, Aug 21, 2020 at 7:50 AM Pavel Yermolenko  > wrote: 
> > 
> > Hi Robert, 
> > 
> > Sorry, I didn't properly understand your message. 
> > I don't remember which branch of u-boot I tried yesterday, but today 
> I've tried with "master" using am335x_boneblack_vboot_defconfig as default 
> configuration. 
>
> No use, the other one.. 
>
> Just run: 
>
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/tools/generate_extlinux.sh
>  
>
> it's under /opt/scripts/tools/ 
>
> It default's to microSD, just tweak it for what you need: 
>
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/tools/generate_extlinux.sh#L16
>  
>
> 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/9b2a7323-b8d2-4f44-a444-54fcaa660478o%40googlegroups.com.

[beagleboard] Re: Can't control LEDs on BBB from terminal

[Dennis Lee Bieber]

On Fri, 21 Aug 2020 06:05:46 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko
 wrote:

>Thanks Dennis,
>
>In my case there is no *gpio, *but *root* 2 times.
>

I'll repeat my previous question: How old is the OS image on that
device?

>debian@beaglebone:~$ ls -l /sys/class/leds/
>total 0
>lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr0 -> 
>../../devices/platform/leds/leds/beaglebone:green:usr0

That "Jan 1 2000" also alarms me, though I am quite sure no Beagle
images go back that far. At best I suspect you have no connection to an NTP
server -- since my system shows a time stamp of yesterday, just before noon
-- which was probably when I ran "sudo apt update" / "sudo apt upgrade -y"


-- 
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/mdlvjf515lvqef4momqckp90jpt2gbp1pc%404ax.com.

Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Robert Nelson]

On Thu, Aug 20, 2020 at 10:13 PM Niresh Kumar  wrote:
>
> We did not make any changes to the .dts file. uEnv.txt file attached for your 
> reference.
>
> There is no script "verison.sh" in the path /opt/scripts/tools/ in kernel 
> version 4.4.30-ti-r64.

Then the version of u-boot is way way way to old. PS, on a newer image
this wouldn't work:

dtb_overlay = /lib/firmware/BB-I2C2-RTC-DS3231.dtbo
->
dtb_overlay=/lib/firmware/BB-I2C2-RTC-DS3231.dtbo

U-Boot's parser doesn't like the "space"...

Feel Free to upgrade.

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/CAOCHtYg_OQ4HtUf99u68Ai4F%2BW%2BA%2BM0JmrqqEguHXKgghhKGSw%40mail.gmail.com.

Re: [beagleboard] Re: Can't control LEDs on BBB from terminal

[Robert Nelson]

On Fri, Aug 21, 2020 at 8:06 AM Pavel Yermolenko  wrote:
>
> Thanks Dennis,
>
> In my case there is no gpio, but root 2 times.
>
> debian@beaglebone:~$ ls -l /sys/class/leds/
> total 0
> lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr0 -> 
> ../../devices/platform/leds/leds/beaglebone:green:usr0
> lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr1 -> 
> ../../devices/platform/leds/leds/beaglebone:green:usr1
> lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr2 -> 
> ../../devices/platform/leds/leds/beaglebone:green:usr2
> lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr3 -> 
> ../../devices/platform/leds/leds/beaglebone:green:usr3
> debian@beaglebone:~$

Your missing this udev rule:

https://github.com/beagleboard/customizations/blob/master/etc/udev/rules.d/88-leds-noroot.rules

sudo apt update ; sudo apt install bb-customizations

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/CAOCHtYjAxnM4ty%3DJxTWf4GG5q1pDrUH%3DKvS0aiqEWgdH4nu%3DMA%40mail.gmail.com.

Re: [beagleboard] Re: Cannot see U-Boot# prompt in terminal

[Robert Nelson]

On Fri, Aug 21, 2020 at 7:50 AM Pavel Yermolenko  wrote:
>
> Hi Robert,
>
> Sorry, I didn't properly understand your message.
> I don't remember which branch of u-boot I tried yesterday, but today I've 
> tried with "master" using am335x_boneblack_vboot_defconfig as default 
> configuration.

No use, the other one..

Just run:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/generate_extlinux.sh

it's under /opt/scripts/tools/

It default's to microSD, just tweak it for what you need:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/generate_extlinux.sh#L16

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/CAOCHtYhkM%3DcmjfCoyZDNTeOO4Tk11bADpS9nu7f%2B5PromPjoqw%40mail.gmail.com.

[beagleboard] Re: Can't control LEDs on BBB from terminal

[Pavel Yermolenko]

Thanks Dennis,

In my case there is no *gpio, *but *root* 2 times.

debian@beaglebone:~$ ls -l /sys/class/leds/
total 0
lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr0 -> 
../../devices/platform/leds/leds/beaglebone:green:usr0
lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr1 -> 
../../devices/platform/leds/leds/beaglebone:green:usr1
lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr2 -> 
../../devices/platform/leds/leds/beaglebone:green:usr2
lrwxrwxrwx 1 root root 0 Jan  1  2000 beaglebone:green:usr3 -> 
../../devices/platform/leds/leds/beaglebone:green:usr3
debian@beaglebone:~$ 


-- 
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/1894e029-42a3-4929-9f1c-db8790d21a77o%40googlegroups.com.

Re: [beagleboard] Re: Cannot see U-Boot# prompt in terminal

[Pavel Yermolenko]

Hi Robert,

Sorry, I didn't properly understand your message.
I don't remember which branch of u-boot I tried yesterday, but today I've 
tried with "master" using *am335x_boneblack_vboot_defconfig *as default 
configuration.

Here is what I see in terminal this time:

U-Boot SPL 2020.10-rc2-00162-g2a4484a5c5 (Aug 21 2020 - 14:14:42 +0200) 
WDT:   Not found! 
Trying to boot from MMC1 
Loading Environment from FAT... *** Warning - bad CRC, using default 
environment 
  
Loading Environment from MMC... *** Warning - bad CRC, using default 
environment 
  
U-Boot 2020.10-rc2-00162-g2a4484a5c5 (Aug 21 2020 - 14:14:42 +0200) 
  
CPU  : AM335X-GP rev 2.1 
Model: TI AM335x BeagleBone Black 
DRAM:  512 MiB 
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1 
Loading Environment from FAT... *** Warning - bad CRC, using default 
environment 
  
Loading Environment from MMC... *** Warning - bad CRC, using default 
environment 
  
 not set. Validating first E-fuse MAC 
Net:   eth2: ethernet@4a10, eth3: usb_ether 
Press SPACE to abort autoboot in 2 seconds 
switch to partitions #0, OK 
mmc0 is current device 
SD/MMC found on device 0 
Failed to load 'boot.scr' 
Failed to load 'uEnv.txt' 
switch to partitions #0, OK 
mmc0 is current device 
Scanning mmc 0:1... 
switch to partitions #0, OK 
mmc0 is current device 
SD/MMC found on device 0 
Failed to load '/boot/zImage' 
switch to partitions #0, OK 
mmc1(part 0) is current device 
Scanning mmc 1:1... 
switch to partitions #0, OK 
mmc1(part 0) is current device 
SD/MMC found on device 1 
** Invalid partition 2 ** 
## Error: "bootcmd_nand0" not defined 
starting USB... 
Bus usb@47401800: Port not available. 
link up on port 0, speed 100, full duplex 
BOOTP broadcast 1 
BOOTP broadcast 2 
BOOTP broadcast 3 
BOOTP broadcast 4 
DHCP client bound to address 10.42.0.39 (3048 ms) 
Using ethernet@4a10 device 
TFTP from server 10.42.0.1; our IP address is 10.42.0.39 
Filename 'zImage'. 
Load address: 0x8200 
Loading: T T T T T T T T T T T T T T T T T T T T 
Retry count exceeded; starting again 
missing environment variable: pxeuuid 
Retrieving file: pxelinux.cfg/01-94-e3-6d-d4-ae-86 
link up on port 0, speed 100, full duplex 
Using ethernet@4a10 device 
TFTP from server 10.42.0.1; our IP address is 10.42.0.39 
Filename 'pxelinux.cfg/01-94-e3-6d-d4-ae-86'. 
Load address: 0x8010 
Loading: T T T T T T T T T T T T T T T T T T T T 
Retry count exceeded; starting again 
Retrieving file: pxelinux.cfg/0A2A0027 
link up on port 0, speed 100, full duplex 
Using ethernet@4a10 device 
TFTP from server 10.42.0.1; our IP address is 10.42.0.39 
Filename 'pxelinux.cfg/0A2A0027'. 
Load address: 0x8010 
Loading: T T T T T T T T T T T T T

Sincerely,

Pavel.



> With mainline generate an extlinux.conf file.
>
> There's a basic script under /opt/scripts/
>
> Sorry on mobile.
>
> Regards,
>

-- 
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/7bf94bff-0e86-4c89-a831-71f8f4894e14o%40googlegroups.com.

[beagleboard] Minimized web app image

[Matthew Juran]

Hello, I recently bought a BeagleBone Black and have been having fun 
working with it for gaming software development purposes. It seems like a 
good host for testing my multiplayer web app game with friends and family 
and for doing benchmarks.

For security on local networks possibly connected to the Internet I’ve 
started with the latest console image 
(bone-eMMC-flasher-debian-10.5-console-armhf-2020-08-12-1gb.img) and made a 
script to customize it after it's installed.

Any ideas of steps to add for security, or feedback about the ones I’m 
doing already? These are highlights:

Change debian and root user passwords.

echo "/dev/mmcblk0  /media/sd  ext4  noatime  0  2" >> /etc/fstab

adduser --system --group --no-create-home --disabled-login myapp

Install the postgres database via apt-get, change the cluster to be on the 
SD card, minimally configure it using the postgres user, and give the myapp 
user access to the app’s tables.

Make my server program a systemd service owned by myapp:myapp with the 
executable and served files on the SD card.

Remove unused packages:

apt-get -y purge bb-bbai-firmware bb-wl18xx-firmware bluez bsdmainutils 
btrfs-progs \
cloud-guest-utils crda dirmngr firmware-atheros firmware-brcm80211 
firmware-iwlwifi \
firmware-libertas firmware-misc-nonfree firmware-realtek 
firmware-zd1211 gdbm-l10n \
gnupg-l10n gnupg-utils gpg-agent gpg gpgconf hostapd iputils-ping iw 
nano-tiny nano \
patch perl-modules-5.28 perl pinentry-curses rfkill wget whiptail \
wireless-regdb wireless-tools wpasupplicant ca-certificates sudo

Some hypothetical steps now are to add firewall rules (only allow inbound 
on port 80 for the app), remove SSH, and remove the debian user. The final 
system is just used by web browsers and maybe an SD card swap, no need to 
access the OS.

Thanks,
Matt

-- 
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/177e7bef-ba38-4824-ad94-89244b147967n%40googlegroups.com.

[beagleboard] Re: Xenoami with working PRUs on Debian in 2020

[Simon K]

I found the problem, for some reason the PRU remoteproc feature was 
disabled => search for ` CONFIG_PRU_REMOTEPROC` in the kernel `.config`.
Don't forget to add the correct overlay to your uEnv.txt and to load the 
modules when configured a module.

Is there any reason the xenomai kernel disables this feature per default or 
can I enable it again?
If so why not set this option to `m` for all BB kernel variants?
supersi...@gmail.com schrieb am Donnerstag, 20. August 2020 um 15:22:17 
UTC+2:

>
> Hi,
>
>
> I am using the pocket beagle for a project and I am unable to set up a 
> proper Xenomai Kernel with working remoteproc (PRUs).
>
> The Kernels I tried lost the /sys/class/remoteproc/remoteproc 1 to 2 
> interface, used to interact with the PRUs as soon as i patched Xenomai.
>
>
>
> This even happened when using the ready to use Xenomai Kernels from 
> RobertCNelson.
> I was not able to find some obvious errors Uboot and the Kernel start up 
> fine, without any error. But dmesg is missing the remoteproc initialisation 
> (but Xenomai seams to run fine).
>
>
> I found a lot of discussion in the forums, but most of it seams to be 
> old/stale information by now.
>
>
> Where to I start to get a Xenomai Kernel with working PRUs, which I can 
> use with the default debian Image?
>
>
> If you could provide me with a few pointers I would be very thankful :)
>

-- 
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/856b7b2b-81a6-4816-91d1-d16dfd6aadd9n%40googlegroups.com.

Re: [beagleboard] How to automatically set system time of BBB by external DS3231

[Tarmo]

On Friday, 21 August 2020 06:13:24 UTC+3, Niresh Kumar wrote:
>
> We did not make any changes to the .dts file. uEnv.txt file attached for 
> your reference.
>
> There is no script "verison.sh" in the path /opt/scripts/tools/ in kernel 
> version 4.4.30-ti-r64. 
>

Wow, you're running a rather old Debian release. The stuff that I suggested 
was likely not implemented back then. I would upgrade to a recent Debian 
release:
http://beagleboard.org/getting-started

Note to whoever maintains beagleboard.org: the Letsencrypt SSL cert expired 
3 days ago.

--
Kind regards,
Tarmo

-- 
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/42bb5db5-cc5a-4104-a2f4-b781ed889bbfo%40googlegroups.com.