Re: [beagleboard] Are the 'latest' builds for BBB really from 2020?
On Mon, Jul 31, 2023 at 11:33 AM Chris Green wrote: > > As per subject, are the latest images for BBB really from April 2020, > it seems rather old. ... or is une just expected to update having > installed? https://forum.beagleboard.org/tag/latest-images -- 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/CAOCHtYindCYWoE-3wkxNFRNX35xSnbcRRq8HiOEUOFyFQQtozw%40mail.gmail.com.
Re: [beagleboard] Re: apt not working - temporary?
On Tue, Apr 25, 2023 at 4:03 PM Chris Green wrote: > > Robert Nelson wrote: > > On Tue, Apr 25, 2023 at 3:33 PM Chris Green wrote: > > > > > > When I try an 'apt update' on my BBB I get the following:- > > > > > > root@odin:~# apt update > > > Ign:1 http://security.debian.org stretch/updates InRelease > > > Err:2 http://security.debian.org stretch/updates Release > > > 404 Not Found [IP: 199.232.170.132 80] > > > Ign:3 http://ftp.us.debian.org/debian stretch InRelease > > > Ign:4 http://ftp.us.debian.org/debian stretch-updates InRelease > > > Err:5 http://ftp.us.debian.org/debian stretch Release > > > 404 Not Found [IP: 208.80.154.139 80] > > > Err:6 http://ftp.us.debian.org/debian stretch-updates Release > > > 404 Not Found [IP: 208.80.154.139 80] > > > Hit:7 https://apt.syncthing.net syncthing InRelease > > > > > > Is there a server down or something? > > > > This is normal, Debian Stretch is EOL, they moved the archive off > > debian.org to 'archive.debian.org' for archival purposes... > > > > https://lists.debian.org/debian-devel-announce/2023/03/msg6.html > > > So what do I need to do to continue keeping my BBB updated? "Updates" ended for Debian Stretch, last summer... You have not gotten any updates in the last 9 months... The only thing that changed, Debian removed the packages for Stretch from their main server... 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/CAOCHtYg8U_cAq62F3RouuEDk_qAFd82d5%3D5fc-f0m4U4Q8fOMw%40mail.gmail.com.
Re: [beagleboard] apt not working - temporary?
On Tue, Apr 25, 2023 at 3:33 PM Chris Green wrote: > > When I try an 'apt update' on my BBB I get the following:- > > root@odin:~# apt update > Ign:1 http://security.debian.org stretch/updates InRelease > Err:2 http://security.debian.org stretch/updates Release > 404 Not Found [IP: 199.232.170.132 80] > Ign:3 http://ftp.us.debian.org/debian stretch InRelease > Ign:4 http://ftp.us.debian.org/debian stretch-updates InRelease > Err:5 http://ftp.us.debian.org/debian stretch Release > 404 Not Found [IP: 208.80.154.139 80] > Err:6 http://ftp.us.debian.org/debian stretch-updates Release > 404 Not Found [IP: 208.80.154.139 80] > Hit:7 https://apt.syncthing.net syncthing InRelease > > Is there a server down or something? This is normal, Debian Stretch is EOL, they moved the archive off debian.org to 'archive.debian.org' for archival purposes... https://lists.debian.org/debian-devel-announce/2023/03/msg6.html 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/CAOCHtYigKT%3DBtcrA%3D-L3ckJ2AoMikA%3DizxAD0YUJ_xGse-X6fg%40mail.gmail.com.
Re: [beagleboard] Re: GPIO JAVA library for Beaglebone Black
On Tue, Jun 29, 2021 at 9:02 AM Radovan Chovan wrote: > > Thanks for all your comments. > > Is there any mapping between /sys/class/gpio and schematic diagram of > Beaglebone Black board? > > I want to use pin P9_24 (UART1_TXD) and P9_26 (UART1_RXD). > https://beagleboard.org/static/beaglebone/BEAGLEBONE_SCHEM_A3.pdf (page 11/11) Derek has this detail on these pdf's https://github.com/derekmolloy/boneDeviceTree/tree/master/docs https://github.com/derekmolloy/boneDeviceTree/blob/master/docs/BeagleboneBlackP9HeaderTable.pdf 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/CAOCHtYi9moXCmnGQJgxUpJZEdgXezBSG%3DpSfZd6N%3DZ-CVyK1WA%40mail.gmail.com.
Re: [beagleboard] GPIO JAVA library for Beaglebone Black
On Wed, Jun 23, 2021 at 8:39 AM Radovan Chovan wrote: > > In the past I used java gpio library libbulldog. > > description from author of library: > https://groups.google.com/g/beagleboard/c/QkdoypqrTPQ/m/L7URLQ1dCAAJ > > http://www.libbulldog.org ... page not found > > Now I am using Debian 10.3 with kernel 4.19.94-ti-r42 in Beaglebone Black. > > Board is detected via command Board board = Platform.createBoard(); > but now I get error: > > java.lang.ArrayIndexOutOfBoundsException: 0 > at > org.bulldog.beagleboneblack.sysfs.BBBSysFs.getCapeManager(BBBSysFs.java:23) > ... > at org.bulldog.core.platform.Platform.createBoard(Platform.java:13) > > From BBBSysFs file: > > private String SYSFS_DEVICES_PATH = "/sys/devices"; > return getFilesInPath(this.SYSFS_DEVICES_PATH, "bone_capemgr")[0]; > > but path sys/devices/bone_capemgr doesn't exist. > > I think problem is in newer kernel: > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Where_did_the_slots_file_go.3F Correct, kernel is too new for that library.. Reboot with 3.8.13, (if it even boots..) 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/CAOCHtYgdnmBWtyH8t13YobJRkWDauo89FOe57Qqd_%2BMAMNay1w%40mail.gmail.com.
Re: [beagleboard] Re: Pocketbeagle Wifi Dongle Problems
On Thu, Jun 10, 2021 at 11:22 AM Patrick Bolton < patrickboltonengin...@gmail.com> wrote: > Well I was hopeful the kernel update today would help with the issues, but > no such luck. > > I powered the board at VIN with a 5VDC 8A power suppy with the 4-usb port > version of 2/4-port USB 2.0 HUB Cape for PocketBeagle from microwavemont > on Tindie > <https://www.tindie.com/products/microwavemont/24-port-usb-20-hub-cape-for-pocketbeagle/> > > Have additional over-current errors. > > If I am not supplying the information that is helpful for solving the > problem, please let me know. > How exactly do you have the usb port wired? https://github.com/beagleboard/pocketbeagle/wiki/FAQ#How_do_I_get_additional_USB_connections 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/CAOCHtYg4EckSRsrGvH0nY%3DyXLxCFzhMjd%3Dk147G8nOpD0s7L4w%40mail.gmail.com.
Re: [beagleboard] Beaglebone AI Device Tree Overlay syntax
On Wed, Jun 9, 2021 at 4:03 PM John Allwine wrote: > > Are we still posting here or should be be posting on the Discourse forum? > > https://forum.beagleboard.org/t/beaglebone-ai-device-tree-overlay-syntax/30044 The discourse forum should be the place. @Jason Kridner is our 2-3 weeks migration up? ;) -- 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/CAOCHtYjRey-UevKjOXF%3DW4PM8QXp1jhn_QQDJJThxQBFztY46w%40mail.gmail.com.
Re: [beagleboard] Invalid module format
On Mon, Jun 7, 2021 at 8:23 AM Paul Beam wrote: > > Thanks, Robert. That would work if I were compiling on the PB, but > cross-compiling on my Debian VM was different. There may be an easier way, > but what I did was follow this: http://phwl.org/2021/building-bbg-kernel/ > to checkout the exact kernel I have on my PB, compile it, and then point my > driver Makefile to this directory. This at least appears to work. Okay, that would also work.. 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/CAOCHtYj2WtF34DOADaLeMxiWL1f170mU3Fdg_2zMJjg7uS9LVg%40mail.gmail.com.
Re: [beagleboard] MachineKit
On Fri, Jun 4, 2021 at 4:59 PM John Dammeyer wrote: > > Robert, > Can you perhaps explain the difference between MachineKit and Linux from the > RTOS perspective? > > I recall something like the Machinekit has the RTOS underneath LinuxCNC where > Linux itself is just a task and the RTOS therefore allows the embedded stuff > to run at the same or higher priority giving better real time support. > > LinuxCNC has a modified kernel that puts the CNC part at a higher priority > within the Linux RTOS environment. > > Have I got that right? I remember reading somewhere there were actually 3 > different versions of 'real time' for Linux. Just don't remember where I > read that. You should really ask the MachineKit developers.. For the BBB, they originally used the Xenomai kernel patchset, then eventually started working on utilizing the RT Linux stuff.. Then they discovered FGPA hardware, shortly after their forum really became quiet.. It's just an application that utilized Xenomai and RT kernel features.. 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/CAOCHtYi83sUF0P9QjQCicvACb1VH-vuB7Qo9tJANq8dsmGkRGw%40mail.gmail.com.
Re: [beagleboard] MachineKit
On Fri, Jun 4, 2021 at 3:09 PM John Dammeyer wrote: > > What's the status with MachineKit for the BBB? Will it ever be resurrected > and brought up to date? My understanding is MachineKit used a different > approach to the RTOS part of real time Linux compared to LinuxCNC running on > say the Pi4. > The BBB image has always been developed and debugged by users of MachineKit.. 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/CAOCHtYj8tUn_o8CjERk5fUAJVX9MWMQ4RcN3VuL21_UJxjb4VQ%40mail.gmail.com.
Re: [beagleboard] Invalid module format
On Fri, Jun 4, 2021 at 4:20 PM Paul Beam wrote: > > I'm trying to build a new driver for a Realtek 8821C for the PocketBeagle, > and although I have managed to cross-compile the module, it fails to load > with an "invalid format" error, which I think means it thinks I compiled with > a different kernel version. > > My PB is still running "4.14-ti", and I downloaded Robert's "rt-4.14" branch > onto my build machine thinking that "4.14" should be close enough. Is my > problem the "ti" branch vs the "rt" branch? I guess I can build it on the PB > if I have to, but it is much faster to build on my desktop and, > theoretically, easier to keep track of. sudo apt install linux-headers-`uname -r` 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/CAOCHtYjKhfodUt6_hfYa1qXaXWQuj4bjfA0hJpaqYw%3DpFm1HiA%40mail.gmail.com.
Re: [beagleboard] Re: BeagleBone Black (C) USB based touch not working
> > The project requires the pru units, that works fine. > Touch is eating up my time. And I expect it makes no sense to order other > touch displays and the status is still the same. > USB based touch was expected as "best and simple" solution. I need SPI and > GPIO for surrounding hardware. That works fine. > HDMI is required to have the possibility to connect "any" monitor. There is > 1m distance between BBB and display. > RPI is not an option for me, because I need the PRU's. lsusb ? i don't see it showing up in dmesg.. 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%3DBonY6FnKgsxP%2B5SEdP1g376ZnAGYXnuFwCY9Tj2Tsw%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
> Be nice not keep downloading the 2G kernel source I know there is a > rebuild.sh but I am assuming that is used after a successful build > If these instruction need I tweek I can understand I can test them. If it old > and not supported a heads up would be appreciated. So I need something like > this below with everything needed to build a kernel including the previous > two steps as my two directories are on the wrong branches There is a variable in system.sh to set this up, most users use it once and done.. https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-5.4.y/system.sh.sample ``` ###OPTIONAL: LINUX_GIT: specify location of locally cloned git tree. # #LINUX_GIT=/home/user/linux-stable/ ``` Anywhere in your root file system, clone Torvald's tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ and set LINUX_GIT variable to it's location: For example in home: cd /home//repos/ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Then set in system.sh LINUX_GIT=/home//repos/linux/ 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/CAOCHtYjWo%3DTrXqp04tkMA31O_fQ%2BJr_SFRz7hDZ_jGw49OS1qA%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 2:53 PM Robert Nelson wrote: > > On Fri, May 28, 2021 at 2:45 PM Robert Nelson wrote: > > > > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz wrote: > > > > > > Thanks!! > > > > > > Think of it as I'm validating the instructions I think having these is > > > something good. Unfortunately my VM blew up just now. > > > > > > I KNOW your adamant about not supporting VM. > > > > > > So I'll build a dedicated Debian 8 dev box. > > > > > > Any hints tips lessons learned what you use be appreciated. > > > > > > Have a great long weekend. > > > > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the > > failure point.. > > I think mainline might work: > > debian@beaglebone:~$ uname -r > 5.13.0-rc3-bone2.2 > debian@beaglebone:~$ dmesg | grep pru > [2.044506] remoteproc remoteproc1: 4a334000.pru is available > [2.045701] remoteproc remoteproc2: 4a338000.pru is available > debian@beaglebone:~$ ls /dev/remoteproc/pruss-core* > /dev/remoteproc/pruss-core0: > coredump device firmware name power recovery state subsystem uevent > > /dev/remoteproc/pruss-core1: > coredump device firmware name power recovery state subsystem uevent > > @Mark Yoder can you test? ;) debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "start" > state [ 243.355728] remoteproc remoteproc1: powering up 4a334000.pru [ 243.366533] remoteproc remoteproc1: Booting fw image am335x-pru0-fw, size 32456 [ 243.374135] remoteproc remoteproc1: remote processor 4a334000.pru is now up debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "stop" > state [ 296.981371] remoteproc remoteproc1: stopped remote processor 4a334000.pru 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/CAOCHtYghrd4aZdh5F85_tGZkEWj4u3MYUst6AKNgzwro8HsEoQ%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 2:45 PM Robert Nelson wrote: > > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz wrote: > > > > Thanks!! > > > > Think of it as I'm validating the instructions I think having these is > > something good. Unfortunately my VM blew up just now. > > > > I KNOW your adamant about not supporting VM. > > > > So I'll build a dedicated Debian 8 dev box. > > > > Any hints tips lessons learned what you use be appreciated. > > > > Have a great long weekend. > > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the > failure point.. I think mainline might work: debian@beaglebone:~$ uname -r 5.13.0-rc3-bone2.2 debian@beaglebone:~$ dmesg | grep pru [2.044506] remoteproc remoteproc1: 4a334000.pru is available [2.045701] remoteproc remoteproc2: 4a338000.pru is available debian@beaglebone:~$ ls /dev/remoteproc/pruss-core* /dev/remoteproc/pruss-core0: coredump device firmware name power recovery state subsystem uevent /dev/remoteproc/pruss-core1: coredump device firmware name power recovery state subsystem uevent @Mark Yoder can you test? ;) 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/CAOCHtYjjHPf9zqKcLYO7_dr4NvaenAnqwyrWaYv8HQwBFWceZw%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz wrote: > > Thanks!! > > Think of it as I'm validating the instructions I think having these is > something good. Unfortunately my VM blew up just now. > > I KNOW your adamant about not supporting VM. > > So I'll build a dedicated Debian 8 dev box. > > Any hints tips lessons learned what you use be appreciated. > > Have a great long weekend. VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the failure point.. 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/CAOCHtYhvPyONo325wtHifsdxO4cFARkFGGuu3K0xdFuBK%3DKNcQ%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 2:19 PM 'Mark Lazarewicz' via BeagleBoard < beagleboard@googlegroups.com> wrote: > Thanks Robert > > I love these instructions very well done > my goal is to be able to build something stable from scratch not drop > binaries maybe modify kernel add drivers be self sufficient at building > everything and manually updating SD card as opposed to using an > upgrade/update on the BB black. > Glad you like it, it's' my old eewiki page just updated and updated as users need help. ;) > > Not worried about having the most current linux wont ask any questions or > need support just trying to learn building everything myself for scratch. I > have NO capes no changes to .dts Im interested in the workings of this > resource file and maybe getting the big shared RAM > Thanks wish I had found this link before did not know it existed > > So I guess my question is which version will work as is for testing some > PRU MSG examples as is? > "as-is"... Either the 4.14.x-ti or 4.19.x-ti with Mark's pru cookbook: https://markayoder.github.io/PRUCookbook/ v5.13.x: closer... just another bug: ebian@beaglebone:~$ uname -r 5.13.0-rc3-bone2.1 debian@beaglebone:~$ dmesg | grep pru [ 2.040720] pruss 4a30.pruss: (null) is missing its 'cfg' node 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/CAOCHtYgW8-jB9B6byJEeB_KFCX6O-s2ObWc-aAzT%2B-hm3PH3Tg%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 1:54 PM Robert Nelson wrote: > > > On Fri, May 28, 2021 at 1:45 PM Robert Nelson > wrote: > >> >> >> On Fri, May 28, 2021 at 1:39 PM 'Mark Lazarewicz' via BeagleBoard < >> beagleboard@googlegroups.com> wrote: >> >>> Dumb question by a Debian Newb >>> >>> I am following this now Debian: Getting Started with the BeagleBone >>> Black >>> <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> >>> >>> Debian: Getting Started with the BeagleBone Black >>> >>> This is a page about TI's Cortex-A8 based; BeagleBone Black. >>> Availability Boards: BeagleBone Black at Digi-K... >>> >>> <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> >>> >>> To test this PRU stuff should I use Mainline or TI BSP? whats the >>> difference? >>> >>> As we speak Im cloning the TI BSP version and looks like somehow I am on >>> 4.14 Branch . I had bad internet last night and I lost the building during >>> resolve after downloading the entire kernel of mainline . Today Im trying >>> TI BSP >>> >>> cloning >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git into >>> default location: /home/lazarman/am335x/ti-linux-kernel-dev/ignore/linux-src >>> >>> >>> >> Use the "am33x-v5.13" branch of: >> https://github.com/RobertCNelson/bb-kernel >> >> There are "pre-builds" under apt... >> >> But, I think we need to update the device tree.. >> > > Thinking: > > > https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/7a960d2e3e04a5418772cddd51493ad8578eccf6 > > And the interrupt controller.. https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/68aea0792284d7b3c58741c62738287762a5cc0c 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/CAOCHtYhN1So9WaXarGMtb6sqP3OES_ZHmvk26WYsG-R5OoZk0g%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 1:45 PM Robert Nelson wrote: > > > On Fri, May 28, 2021 at 1:39 PM 'Mark Lazarewicz' via BeagleBoard < > beagleboard@googlegroups.com> wrote: > >> Dumb question by a Debian Newb >> >> I am following this now Debian: Getting Started with the BeagleBone Black >> <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> >> >> Debian: Getting Started with the BeagleBone Black >> >> This is a page about TI's Cortex-A8 based; BeagleBone Black. Availability >> Boards: BeagleBone Black at Digi-K... >> >> <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> >> >> To test this PRU stuff should I use Mainline or TI BSP? whats the >> difference? >> >> As we speak Im cloning the TI BSP version and looks like somehow I am on >> 4.14 Branch . I had bad internet last night and I lost the building during >> resolve after downloading the entire kernel of mainline . Today Im trying >> TI BSP >> >> cloning >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git into >> default location: /home/lazarman/am335x/ti-linux-kernel-dev/ignore/linux-src >> >> >> > Use the "am33x-v5.13" branch of: > https://github.com/RobertCNelson/bb-kernel > > There are "pre-builds" under apt... > > But, I think we need to update the device tree.. > Thinking: https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/7a960d2e3e04a5418772cddd51493ad8578eccf6 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/CAOCHtYgDgNBuGh05MRkN8BLmJ%3DUvc9wZgY6vOVCdMiS4rHfeYA%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 1:39 PM 'Mark Lazarewicz' via BeagleBoard < beagleboard@googlegroups.com> wrote: > Dumb question by a Debian Newb > > I am following this now Debian: Getting Started with the BeagleBone Black > <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> > > Debian: Getting Started with the BeagleBone Black > > This is a page about TI's Cortex-A8 based; BeagleBone Black. Availability > Boards: BeagleBone Black at Digi-K... > > <https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967> > > To test this PRU stuff should I use Mainline or TI BSP? whats the > difference? > > As we speak Im cloning the TI BSP version and looks like somehow I am on > 4.14 Branch . I had bad internet last night and I lost the building during > resolve after downloading the entire kernel of mainline . Today Im trying > TI BSP > > cloning https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > into default location: > /home/lazarman/am335x/ti-linux-kernel-dev/ignore/linux-src > > > Use the "am33x-v5.13" branch of: https://github.com/RobertCNelson/bb-kernel There are "pre-builds" under apt... But, I think we need to update the device tree.. 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/CAOCHtYjoJEDJgvnwdcz%2B-3ktqFCTmyebB3qF41g2mMSGij1hiA%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 12:53 PM Robert Nelson wrote: > > On Fri, May 28, 2021 at 12:51 PM Robert Nelson > wrote: > > > > On Fri, May 28, 2021 at 12:47 PM Bruce Chidester > > wrote: > > > > > > Does the 5.x kernel support an interrupt from the PRU while also > > > supporting the bi-directional messaging through rproc? > > > > sorry, i completely missed these commits, so i have not personally > > tested it... It got merged in v5.11.x and has been tweaked since.. > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml?h=v5.13-rc3 > > > > it "should" be an extension of the pru code found in > > v4.14.x-ti/v4.19.x-ti/v5.4.x-ti.. > > I see lots of interrupt hints here: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/remoteproc/pru_rproc.c irq driver for pru: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/irqchip/irq-pruss-intc.c 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/CAOCHtYjHr%3D2Mx%2BKLa9enn2pd9rfid0SQ6kVw7ZNh8RPgJpZiFA%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 12:51 PM Robert Nelson wrote: > > On Fri, May 28, 2021 at 12:47 PM Bruce Chidester > wrote: > > > > Does the 5.x kernel support an interrupt from the PRU while also supporting > > the bi-directional messaging through rproc? > > sorry, i completely missed these commits, so i have not personally > tested it... It got merged in v5.11.x and has been tweaked since.. > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml?h=v5.13-rc3 > > it "should" be an extension of the pru code found in > v4.14.x-ti/v4.19.x-ti/v5.4.x-ti.. I see lots of interrupt hints here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/remoteproc/pru_rproc.c 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/CAOCHtYhhPL8UMw14fV9rvJviCFvpbviWNuxaU8pxepVX42G4CQ%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 12:47 PM Bruce Chidester wrote: > > Does the 5.x kernel support an interrupt from the PRU while also supporting > the bi-directional messaging through rproc? sorry, i completely missed these commits, so i have not personally tested it... It got merged in v5.11.x and has been tweaked since.. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml?h=v5.13-rc3 it "should" be an extension of the pru code found in v4.14.x-ti/v4.19.x-ti/v5.4.x-ti.. 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/CAOCHtYj40mHeMBVKHq%2B9jZ00c%2BqOBqs%3DFA%2BNSYOK4cFwsQ4hiQ%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 12:36 PM Robert Nelson wrote: > > On Fri, May 28, 2021 at 12:21 PM Bruce Chidester > wrote: > > > > I'm confused because I thought the plan was Remote Proc going forward. Do > > you seem to say it is UIO going forward? > > Mainline has been 'slowly' getting RemoteProc work done by TI.. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/remoteproc/pru_rproc.c 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/CAOCHtYjY_bTHv4TyhMbuu-J9m8V8gbo810t%2BWh9d2d-S62LLow%40mail.gmail.com.
Re: [beagleboard] Re: PRU Assumptions - True or False
On Fri, May 28, 2021 at 12:21 PM Bruce Chidester wrote: > > I'm confused because I thought the plan was Remote Proc going forward. Do you > seem to say it is UIO going forward? Mainline has been 'slowly' getting RemoteProc work done by TI.. 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/CAOCHtYh_GaR%2BHQgGSogRKoHegfdjvRpxe_jn7N3UARmiTwcxgQ%40mail.gmail.com.
Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black
On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal wrote: > > @Dennis L Bieber Really thanks for your detailed explanation about the each > services. > I also updated ubuntu from 16 to 18 and done some modification in the > services. now my board's logs are as below > My system should be working as station mode but may be future, we will add AP > mode also. > I will also remove nginx services. > > > ubuntu@beaglebone:~$ systemd-analyze blame > 51.048s dev-mmcblk1p1.device > 28.951s generic-board-startup.service > 6.550s led-status.service > 6.133s systemd-hwdb-update.service > 4.805s grub-common.service > 4.611s loadcpufreq.service > 3.244s nginx.service > 3.053s systemd-udev-trigger.service > 2.971s avahi-daemon.service > 2.099s ssh.service > 1.958s archive_log.service > 1.839s keyboard-setup.service > 1.548s rsyslog.service > 1.512s connman.service > 1.438s systemd-user-sessions.service > 1.404s wpa_supplicant.service > 1.315s ofono.service > 1.291s systemd-logind.service > 1.275s cpufrequtils.service > 1.253s tacread-keymap.service >887ms systemd-timesyncd.service >786ms user@0.service >685ms systemd-journald.service >508ms kmod-static-nodes.service >498ms dev-mqueue.mount >487ms fake-hwclock.service >469ms sys-kernel-config.mount >459ms systemd-fsck-root.service >422ms systemd-tmpfiles-setup-dev.service >406ms systemd-modules-load.service >401ms systemd-sysctl.service >390ms systemd-tmpfiles-setup.service >387ms setvtrgb.service >350ms nvda.service >341ms sys-fs-fuse-connections.mount > > > Also want to know that in ubuntu 18, why below two task taking so much time > and how we can reduce it further to achieve the over all boot time as 30 sec. > Any suggestion will help me. > > 51.048s dev-mmcblk1p1.device > 28.951s generic-board-startup.service as long as you don't use usb-serial, usb-flash, or usb-networking on the "OTG" USB port, you can nuke generic-board-startup.service 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/CAOCHtYgLWHEPsyhJE-CuqE%2BWnSBHQkdzPDrdjqM0JSWcU%3D_Q0A%40mail.gmail.com.
Re: [beagleboard] Re: ioctl messages to Beagle SPI port.
On Fri, May 21, 2021 at 11:54 AM John Dammeyer wrote: > > Gawd, I can't even get the math right. 8 blocks of 4096 make up 32K. > > At the moment I suspect one of my 320x240 displays might be toast. Even the > Python code doesn't light up the screen and that used to work. But it was > way back on an OS with $SLOTs. If you want to verify it, the old 3.8.x based kernel is still in apt repo.. 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/CAOCHtYiRfWP0OcfzL32uBQmrNMSKED%2BK0g0Z64uwE6J%3DfVrteg%40mail.gmail.com.
Re: [beagleboard] Re: ioctl messages to Beagle SPI port.
On Fri, May 21, 2021 at 11:40 AM John Dammeyer wrote:
>
> Thanks Dennis,
>
>
> > -Original Message-
> > From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
> > Behalf Of Dennis Lee Bieber
> > "John Dammeyer" wrote:
> >
> >
> > >The sad thing is that Derek Molloy's book, only in passing refers to
> > >enabling the SPI port, and the book, in trying to also deal with the
> > pocket beagle pins leaves out things where repetition is actually
> > beneficial. Maybe somewhere it says that you have to use config-pin
> > to set up SPI. I missed it. I think in Chapter 8 page 363 needs a bit of
> > work.
> >
> > One: you have to look at the default pin-mux tables -- the default for
> > many is as GPIO.
> >
> > Two: config-pin is discussed in chapter 6 (which also has a
> > hard-to-read version of the tables). It doesn't mention SPI explicitly, but
> > does mention that the tool is used in later chapters.
>
> My posting from
> Fri 14/05/2021
> RE: [beagleboard] Configure CAN0 with buildroot
>
> talks about using config-pin for CAN bus. I spent so much time a number of
> years ago learning about SLOTs and spending time even writing my own DTS for
> a proto board that has a 1-wire sensor. The Logic Supply CAN cape dts was
> also used.
>
> I can't seem to completely unlearn (if that's the right term) and now still
> get very confused as to what to use and when.
>
> So I guess I should have remembered that on the 14th of May I did use
> config-pin for CAN so it must also be needed for SPI.
>
>
> >
> > debian@beaglebone:~$
> > /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i
> > p9_18
> > Pin name: P9_18
> > Function if no cape loaded: gpio
> > Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input spi i2c
> > pwm pru_uart
>
> I've done that with the pins. But again my incorrect assumption was that the
> OS was intelligent enough that if I do:
>
> static const char *device = "/dev/spidev1.0";
> fd = open(device, O_RDWR);
> if (fd < 0)
> pabort("can't open device");
>
> One of two things happen. Either It opens the SPI bus which includes
> everything that config-pin does or it fails because config-pin wasn't done.
> In fact I believe that until the config-pin operations on the SPI pins is
> done that the /dev/spidev1.0 shouldn't exist. That they are there is
> incorrect information.
>
> But this is 'human factors engineering" which the Beagle (Linux?) lacks in a
> big way.
>
>
> > >Oh and none of this explains why the ioctl regardless of C or Pascal
> > >
> can't handle more than 4096 data bytes while the Python code can when sending
> a large bitmap to the SPI port.
> ...
> > debian@beaglebone:~$ cat /sys/module/spidev/parameters/bufsiz
> > 4096
> > debian@beaglebone:~$
>
> How did you know to look at this file to determine the SPI buf size?
>
> I see that it's a read only file.
> debian@ebb:~$ ls -al /sys/module/spidev/parameters/bufsiz
>-r--r--r-- 1 root gpio 4096 May 20 16:45
> /sys/module/spidev/parameters/bufsiz
>
> The code I'm adapting from a 128x128 display sends out a 512x512 lenna.jpg
> compressed into a smaller window. Even so any sort of bit map object that is
> 128x128x16 for example is 32K in size. So no matter what sort of canvas I
> draw on inside the application, to render it out to an SPI display still
> requires 9 blocks of 4096 bytes.
>
> I'll look into that. Really don't want to write in Python.
>
> > A lot of that is a bit out-of-date -- references to kernel 3.8! Though
> > I do have to admit I can't find where in Adafruit_BBIO it might do that
> > set-up -- it doesn't seem to be done in the above spidev Python interface,
> > which is used by (now deprecated in favor of blinka/circuitpython)
> > Adafruit_BBIO... And I can't find a config change in blinka or
> > Adafruit_PureIO. {PureIO may not invoke the above spidev module, so how
> > /it/ handles large blocks is unknown}
>
> I was going to suggest that the BBB is now an out of date product but
> https://www.digikey.ca/en/products/detail/beagleboard-by-seeed-studio/102110420/12719590
> shows over 4000 in stock. So maybe not?
The am335x based BBB is going to be around for a long time to come...
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/CAOCHtYiEkosdy88FSb2aYDpwwOoLRjOpCPbN8wOi%3DV-AZ8oj4A%40mail.gmail.com.
Re: [beagleboard] Reducing Boottime in Beaglebone Black
> removed wpasupplicant and connman and old kernel > > sudo apt-get purge linux-image-4.14.108-ti-r134 wpasupplicant connman > > debian@beaglebone:~$ systemd-analyze > > Startup finished in 13.502s (kernel) + 36.686s (userspace) = 50.188s > > I then removed the initrd file in /boot directory (From what I understand > this kernel does not necessarily need initrd). > debian@beaglebone:/boot$ sudo mv initrd.img-4.19.94-ti-rt-r63 > moved-initrd.img-4.19.94-ti-rt-r63 > > Removing the initrd gives the max speedup for kernel. From 10s-13s with > initrd, it reduces to 1s-2s > debian@beaglebone:~$ systemd-analyze > Startup finished in 1.663s (kernel) + 36.385s (userspace) = 38.048s > debian@beaglebone:~$ systemd-analyze blame > 1min 4.266s dev-mmcblk1p1.device > 26.360s generic-board-startup.service > 3.847s systemd-udev-trigger.service > 2.824s loadcpufreq.service You can nuke this ^, it's really only for am57xx, so we can downclock.. But on am335x, let it run at full speed as these are set: CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y > 2.215s networking.service > 1.647s ssh.service > 1.396s user@1000.service > 1.209s rsyslog.service > 1.189s systemd-journald.service >999ms dnsmasq.service >897ms cpufrequtils.service Same as above.. >855ms systemd-timesyncd.service >674ms systemd-fsck-root.service >642ms systemd-logind.service >505ms systemd-udevd.service >445ms systemd-user-sessions.service >408ms systemd-tmpfiles-setup-dev.service >389ms systemd-update-utmp.service >375ms hostapd.service You nuked wpasupplicant, get rid of hostapd.. >365ms systemd-modules-load.service >326ms dev-mqueue.mount >324ms systemd-random-seed.service >312ms sys-kernel-config.mount >291ms systemd-tmpfiles-setup.service >274ms sys-kernel-debug.mount >236ms kmod-static-nodes.service >231ms sys-fs-fuse-connections.mount >200ms systemd-remount-fs.service >190ms systemd-journal-flush.service >185ms systemd-sysctl.service >145ms systemd-update-utmp-runlevel.service >130ms systemd-tmpfiles-clean.service > > Next point to attack is the generic-board-startup.service. The main time that > process spends is in the file /opt/scripts/boot/am335x_evm.sh > This takes care of the USB flash, Serial and network gadgets that are > initialized. Remove items which are not needed. It also has a lot of generic > selections for Beagle family boards which can be removed. I am working on my > version for just beaglebone black with only network over USB support. > Some ideas can be found here > (https://github.com/RobertCNelson/boot-scripts/issues/10) > > Hope that helps. -- 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/CAOCHtYiuY6ECN7pemXO%2B5CRKH4sEixN3%3DKhL6-BijrY7H%2BNoYg%40mail.gmail.com.
Re: [beagleboard] Re: Unable to boot from SD card or mount a blank one
On Tue, May 18, 2021 at 6:28 PM Shrikumar Sharma wrote: > > Thank you for your answers. However, the board never recognizes the SD card... What is the image name of the file, you flashed with etcher.io to your SD card? 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/CAOCHtYjYrPcQGzjy5byuYiJhdKZtm5LHOi_Q%3DUy8vgjKQ4AMgg%40mail.gmail.com.
Re: [beagleboard] Configure CAN0 with buildroot
On Sun, May 16, 2021 at 8:55 PM John Dammeyer wrote: > > Oh and just for interest. Boot a Pi3 with Linux raspberrypi 5.10.17-v7+ and > nothing in the USB port and screen shows up as expected. Plug same 4 port > hub with the connect the the USB switch and a 4GB USB drive. Then press the > button to change from workstation to Pi and about 5 seconds later the mouse > and keyboard work nd in the /media/pi/Transcend are the files on the USB > drive. > > On the Beagle the little blue LED on the USB drive doesn't even light up. > > I kind of think the BBB should be able to do this too. Is the USB hub powered externally? How are you powering the Beagle? 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/CAOCHtYhjrJ6yBNw59zLZyG2YJ1aXHW3zcyHuH7DUAwz_GFYWow%40mail.gmail.com.
Re: [beagleboard] Re: Unable to boot from SD card or mount a blank one
The am57xx boot rom defaults to microsd before emmc... On Sun, May 16, 2021, 3:07 PM Dennis Lee Bieber wrote: > On Sun, 16 May 2021 09:49:02 -0700, in gmane.comp.hardware.beagleboard.user > "John Dammeyer" wrote: > > >If it's like the Beaglebone Black, when you apply power, you have to > hold the boot button down for quite a while.That's what tells the > system to boot from the sd card. > > > > That has only applied to very old BBB eMMC images... Sometime in > the > late Wheezy or mid-Jessie era, u-Boot was modified to automatically search > for a uSD card image, and transfer control to the SD card if found. > > I haven't had to touch the boot select switch in something like 3+ > years. > > Note: the BB AI does not have a boot select switch -- it expects > the > eMMC u-Boot to do the switching if a proper card is found. > > > -- > 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/gnu2agtirijnefdifu8ogutmo8amqhj2u7%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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhPtpP9%3DJE8QqcJGTXJs-R8oL_MD77FqeK1BcBYik%2BvSA%40mail.gmail.com.
Re: [beagleboard] Configure CAN0 with buildroot
On Fri, May 14, 2021 at 9:24 PM John Dammeyer wrote: > > I moved the MicroSD card over to the other Beagle. Booted and USB mouse and > keyboard (Logitech wireless) work. The Logitech wireless was not discovered > on the other Beagle. > > > > I think it may be sick. > > > > > > Last login: Fri May 14 18:11:06 2021 from 192.168.0.137 > > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > > [sudo] password for debian: > > git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0] > > eeprom:[A335BNLT00C02716BBBK0E8D] > > model:[TI_AM335x_BeagleBone_Black] > > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +)]:[location: dd MBR] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-g10968f0]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL > 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2019.04-2-gbb4af0f50f]:[location: dd MBR] > > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts] > > UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-14-TI-00A0] > > UBOOT: Loaded Overlay:[BB-ADC-00A0] > > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] > > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0] > > kernel:[4.14.108-ti-r141] > > nodejs:[v6.17.0] > > /boot/uEnv.txt Settings: > > uboot_overlay_options:[enable_uboot_overlays=1] > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] > > uboot_overlay_options:[enable_uboot_cape_universal=1] > > pkg check: to individually upgrade run: [sudo apt install --only-upgrade > ] > > pkg:[bb-cape-overlays]:[4.14.20210416.0-0~stretch+20210416] > > pkg:[bb-customizations]:[1.20210225.0-0~stretch+20210225] > > pkg:[bb-usb-gadgets]:[1.20200504.0-0~stretch+20200504] > > pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813] > > pkg:[kmod]:[23-2rcnee1~stretch+20171005] > > pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716] > > pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305] > > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev > users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi > tisdk weston-launch xenomai] > > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 quiet] > > dmesg | grep remote > > [1.108680] remoteproc remoteproc0: wkup_m3 is available > > [1.453877] remoteproc remoteproc0: powering up wkup_m3 > > [1.453993] remoteproc remoteproc0: Booting fw image > am335x-pm-firmware.elf, size 217148 > > [1.458014] remoteproc remoteproc0: remote processor wkup_m3 is now up > > [ 165.380047] remoteproc remoteproc1: 4a334000.pru is available > > [ 165.395267] remoteproc remoteproc2: 4a338000.pru is available > > dmesg | grep pru > > [ 163.347677] pruss 4a30.pruss: creating PRU cores and other child > platform devices > > [ 165.380047] remoteproc remoteproc1: 4a334000.pru is available > > [ 165.380228] pru-rproc 4a334000.pru: PRU rproc node > /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully > > [ 165.395267] remoteproc remoteproc2: 4a338000.pru is available > > [ 165.395389] pru-rproc 4a338000.pru: PRU rproc node > /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully > > dmesg | grep pinctrl-single > > [0.796710] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size > 568 > > dmesg | grep gpio-of-helper > > [0.809442] gpio-of-helper ocp:cape-universal: ready > > lsusb > > Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver > > Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > END > > debian@beaglebone:~$ > > > > I then created an sd card with this > > bone-debian-10.3-console-armhf-2020-04-06-1gb.img.xz > > Login prompt on screen with USB keyboard functioning. > > This is without the CAN Cape. I've attached the serial port terminal log. > > > > Next I'll shut it down and put the cape back. > > > > From the descriptions on https://beagleboard.org/latest-images I can't figure > out what the latest graphical desktop image is for the BBB. There really isn't an official lxqt release, it just was too un-
Re: [beagleboard] Configure CAN0 with buildroot
Does USB work after 30-45 seconds? If so, still trying to debug that.. On Fri, May 14, 2021, 7:23 PM John Dammeyer wrote: > Hi Robert, > Not that set in stone really. Just that the last time I did one of those > "you must upgrade to get support" I ended up buying a new edition of Derek > Molloy's book because the $SLOTs stuff vanished which also made 5 other > books I have on the Beagle pointless for the most part. > > Between editions and versions my 4DCape LCD display also no longer worked > so it's in the box of useless LCD displays along with the Manga 1 (never > worked right) and Manga2. > > How much of the step by step instructions in Derke Molloy's (c) 2019 2nd > edition are voided and how will I know what is supposed to work and not. > > I've done the following. > cd /opt/scripts/tools/ > sudo ./update_kernel.sh > # and reboot.. > now run: > sudo /opt/scripts/tools/version.sh > > >We should see a more friendly setup. ;) > > = > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > [sudo] password for debian: > git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0] > eeprom:[A335BNLT00C02814BBBK0472] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +)]:[location: dd MBR] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-g10968f0]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2019.04-g10968f0 > (Feb 19 2021 - 21:40:51 +)]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2019.04-g10968f0]:[location: dd MBR] > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts] > UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-14-TI-00A0] > UBOOT: Loaded Overlay:[BB-ADC-00A0] > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0] > UBOOT: Loaded Overlay:[cape-CBB-Serial-r01] > kernel:[4.14.108-ti-r141] > nodejs:[v6.17.0] > /boot/uEnv.txt Settings: > uboot_overlay_options:[enable_uboot_overlays=1] > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg check: to individually upgrade run: [sudo apt install --only-upgrade > ] > pkg:[bb-cape-overlays]:[4.14.20210416.0-0~stretch+20210416] > pkg:[bb-customizations]:[1.20210225.0-0~stretch+20210225] > pkg:[bb-usb-gadgets]:[1.20200504.0-0~stretch+20200504] > pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813] > pkg:[kmod]:[23-2rcnee1~stretch+20171005] > pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716] > pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305] > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video > plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep > admin spi tisdk weston-launch xenomai] > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait > uboot_detected_capes=cape-CBB-Serial, coherent_pool=1M net.ifnames=0 quiet] > dmesg | grep remote > [1.096197] remoteproc remoteproc0: wkup_m3 is available > [1.440935] remoteproc remoteproc0: powering up wkup_m3 > [1.441056] remoteproc remoteproc0: Booting fw image > am335x-pm-firmware.elf, size 217148 > [1.445403] remoteproc remoteproc0: remote processor wkup_m3 is now up > dmesg | grep pru > dmesg | grep pinctrl-single > [0.796756] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 > size 568 > dmesg | grep gpio-of-helper > [0.809620] gpio-of-helper ocp:cape-universal: ready > lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > END > debian@beaglebone:~$ > == > > Sees the cape now. Mouse and keyboard no longer work. In fact USB > doesn't work at all. > John > > > > > > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2015.01-1-gb2412df]:[location: dd MBR] > > > > Oh fun, 2018 wth 2015 causing issues.. > > > > how set in stone are your for "2018-10-07" Release? > > > > 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/CAOCHtYix%2B9yHdarF7JbbrkagUdH-JX-0sE1dbiyKqkNs-dAoHw%40mail.gmail.com.
Re: [beagleboard] Configure CAN0 with buildroot
On Fri, May 14, 2021 at 6:09 PM Robert Nelson wrote: > > On Fri, May 14, 2021 at 4:58 PM John Dammeyer wrote: > > > > So here's the results of version.sh from both beagles. The rev 141 > > doesn't see the cape_CBB_Serial-r01 from Logic Supply as shown in the > > photo. For convenience I've also included the side by side compare of the > > two files. > > > > Not sure why this install doesn't see the cape. > > > > Last login: Fri May 14 00:16:10 2021 from 192.168.0.137 > > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > > [sudo] password for debian: > > git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0] > > eeprom:[A335BNLT00C02814BBBK0472] > > model:[TI_AM335x_BeagleBone_Black] > > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > > 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)]:[location: dd MBR] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > > 2018.09-2-g0b54a51eee]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL > > 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > > 2015.01-1-gb2412df]:[location: dd MBR] > > Oh fun, 2018 wth 2015 causing issues.. > > how set in stone are your for "2018-10-07" Release? If you want to keep: "2018-10-07" here's what i would do: #Good bye 2015 bootloader: sudo apt update sudo apt install bb-u-boot-am335x-evm cd /opt/u-boot/bb-u-boot-am335x-evm/ sudo ./install.sh #Latest v4.14.x-ti: cd /opt/scripts/tools/ sudo ./update_kernel.sh # and reboot.. now run: sudo /opt/scripts/tools/version.sh We should see a more friendly setup. ;) 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/CAOCHtYiBV6qLbz-R0QgW8YiY5D0E1w59XBR3%2BgCfpnxNfti%2Bsg%40mail.gmail.com.
Re: [beagleboard] Configure CAN0 with buildroot
On Fri, May 14, 2021 at 4:58 PM John Dammeyer wrote: > > So here's the results of version.sh from both beagles. The rev 141 doesn't > see the cape_CBB_Serial-r01 from Logic Supply as shown in the photo. For > convenience I've also included the side by side compare of the two files. > > Not sure why this install doesn't see the cape. > > Last login: Fri May 14 00:16:10 2021 from 192.168.0.137 > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > [sudo] password for debian: > git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0] > eeprom:[A335BNLT00C02814BBBK0472] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[BeagleBoard.org Debian Image 2018-10-07] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)]:[location: dd MBR] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2018.09-2-g0b54a51eee]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2015.01-1-gb2412df > (Jan 29 2015 - 15:01:06)]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2015.01-1-gb2412df]:[location: dd MBR] Oh fun, 2018 wth 2015 causing issues.. how set in stone are your for "2018-10-07" Release? 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/CAOCHtYjHsnpiF9LDEFTejpR540WNpir5DpPkakTOkzxCUtiXpg%40mail.gmail.com.
Re: [beagleboard] Configure CAN0 with buildroot
On Fri, May 14, 2021 at 1:46 PM johnd wrote: > > Ah. So it doesn't apply to Debian. Thanks For Debian, it's enabled out of the box, just use config-pin to change it from i2c to can.. If it doesn't work, report back with: sudo /opt/scripts/tools/version.sh 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/CAOCHtYjG7re-hHGipru51L5euS-bae5FN-wNMuRfquZGvnKhMA%40mail.gmail.com.
Re: [beagleboard] versioning beaglebone images with OSTree
On Tue, May 4, 2021 at 5:28 PM John Allwine wrote: > > Where is the source code for what u-boot runs by default on the Beaglebone > images? I see some references to patches that I assume are applied to u-boot > on the Beaglebone: > https://github.com/beagleboard/image-builder/blob/master/target/chroot/beagleboard.org-buster.sh#L276-L291 > > Is there somewhere I can see the applied versions of those or do I have to > manually apply them? I'm trying to understand what exactly the environment > variables in uEnv.txt do. You can find that tree here: https://github.com/beagleboard/u-boot/tree/v2019.04-bbb.io-am335x it's built/provided via the debian package: bb-u-boot-am335x-evm https://github.com/rcn-ee/repos/tree/master/bb-u-boot-am335x-evm 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/CAOCHtYhryUMyNwDDw1FssnSTbToaoFmgcJrcQJka%3D23RCMyMjQ%40mail.gmail.com.
Re: [beagleboard] Beaglebone AI eMMC flasher
On Tue, Apr 27, 2021 at 12:05 PM Pedro Cruz wrote: > > Hello Robert, > > Attached is a trace file. I am using the file > am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img and I burned it > into SDCARD by using the balena tool. > > If I boot with the regular card, I don't see /dev/mmcblk1 in the ls /dev > command. > Could it be a damaged nand flash memory? > > Also, I see that the boot program doesn't have any nand test utility which is > common to other Linux uboot systems. > > Best Regards, Hi Pedro, There is something wrong with your eMMC, your log has a few issues: In u-boot: Card did not respond to voltage select! invalid mmc device (that's your eMMC) in the boot log you have: [2.859012] mmc1: SDHCI controller on 480b4000.mmc [480b4000.mmc] using ADMA You should see: [2.866958] mmc1: SDHCI controller on 480b4000.mmc [480b4000.mmc] using ADMA [3.048201] mmc1: new HS200 MMC card at address 0001 [3.054153] mmcblk1: mmc1:0001 TB2916 14.6 GiB [3.074388] mmcblk1boot0: mmc1:0001 TB2916 partition 1 4.00 MiB [3.101629] mmcblk1boot1: mmc1:0001 TB2916 partition 2 4.00 MiB [3.115591] mmcblk1rpmb: mmc1:0001 TB2916 partition 3 4.00 MiB, chardev (245:0) [3.157241] mmcblk1: p1 Here's a quick test with that image.. 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/CAOCHtYiB0Vhd3sE3eFhhBBWGToCeKvT4t4XXHVQQh9fXD9XL7A%40mail.gmail.com. U-Boot 2019.07-rc4-1-g607b5b738b (Jul 06 2019 - 21:01:15 -0500), Build: jenkins-github_Bootloader-Builder-127 CPU : DRA752-GP ES2.0 Model: BeagleBoard.org BeagleBone AI Board: BeagleBone AI REV A DRAM: 1 GiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 CTRL_CORE_PAD_I2C1_SDA:0x0006 CTRL_CORE_PAD_I2C1_SCL:0x0006 CTRL_CORE_PAD_GPMC_A0: 0x00060007 CTRL_CORE_PAD_GPMC_A1: 0x00060007 CTRL_CORE_PAD_VIN2A_D4:0x0005000f CTRL_CORE_PAD_VIN2A_D5:0x0005000f CM_L4PER_GPIO7_CLKCTRL:0x0001 CM_L4PER_I2C1_CLKCTRL: 0x0002 CM_L4PER_I2C4_CLKCTRL: 0x0002 CM_L4PER_L4_PER1_CLKCTRL 0x0001 PM_L4PER_I2C1_WKDEP0xb000 RM_L4PER_I2C1_CONTEXT 0x0002 PM_L4PER_I2C4_WKDEP0xb000 RM_L4PER_I2C4_CONTEXT 0x0001 BeagleBone: cape eeprom: i2c_probe: 0x54 Checking (ret 1 bus works) I2C1 bus. ret 1 Checking (ret 1 bus works) I2C4 bus. ret 1 BeagleBone: cape eeprom: i2c_probe: 0x55 Checking (ret 1 bus works) I2C1 bus. ret 1 Checking (ret 1 bus works) I2C4 bus. ret 1 BeagleBone: cape eeprom: i2c_probe: 0x56 Checking (ret 1 bus works) I2C1 bus. ret 1 Checking (ret 1 bus works) I2C4 bus. ret 1 BeagleBone: cape eeprom: i2c_probe: 0x57 Checking (ret 1 bus works) I2C1 bus. ret 1 Found device at address 0x57 Net: Warning: ethernet@48484000 using MAC address from ROM eth0: ethernet@48484000 Press SPACE to abort autoboot in 1 seconds usb_boot is currently disabled scsi_boot is currently disabled switch to partitions #0, OK mmc0 is current device Partition Map for MMC device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUID Type 1 8192 7364608 039c5d23-01 83 Boot Scanning mmc device 0 Checking for: /uEnv.txt ... Checking for: /boot/uEnv.txt ... 449 bytes read in 1 ms (438.5 KiB/s) Loaded environment from /boot/uEnv.txt Checking if uname_r is set in /boot/uEnv.txt ... debug: [uname_r=4.19.94-ti-r42] ... loading /boot/vmlinuz-4.19.94-ti-r42 ... 10095592 bytes read in 870 ms (11.1 MiB/s) loading /boot/dtbs/4.19.94-ti-r42/am5729-beagleboneai.dtb ... 137339 bytes read in 16 ms (8.2 MiB/s) uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable... loading /boot/initrd.img-4.19.94-ti-r42 ... 6589689 bytes read in 568 ms (11.1 MiB/s) debug: [console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3-no-eeprom.sh] ... debug: [bootz 0x8200 0x8808:648cf9 0x8800] ... ## Flattened Device Tree blob at 8800 Booting using the fdt blob at 0x8800 Loading Ramdisk to 8f9b7000, end 8cf9 ... OK Loading Device Tree to 8f992000, end 8f9b687a ... OK Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) (gcc version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 [0.00] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d [0.00] CPU: div instructions available: patching division code [0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [0.00] OF: fdt
Re: [beagleboard] building something from source in image-builder script
On Tue, Apr 27, 2021 at 1:59 PM John Allwine wrote: > > It seems like that tmp dir is missing a lot of data. Is there a clean up step > I need to comment out? If you kill it right here: https://github.com/beagleboard/image-builder/blob/master/scripts/chroot.sh#L1363 You can re-chroot in.. 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/CAOCHtYiv_2LRS_xNUt88yfH2zWn05v2QcinGU%2BXwTfv%2ByELxMg%40mail.gmail.com.
Re: [beagleboard] building something from source in image-builder script
On Tue, Apr 27, 2021 at 1:36 PM John Allwine wrote: > > Is there a way to drop into a bash terminal within the qemu environment to > debug? I ran the RootStock-NG.sh script and see the ignore/tmp.X > directory. Does something like this work? > > After running RootStock-NG.sh; > sudo chroot /path/to/ignore/tmp.XXX /bin/bash > > (I get a /lib/ld-linux-armhf.so.3: No such file or directory when I do that) Before you chroot, make sure you mount sys, proc, dev/pts https://github.com/beagleboard/image-builder/blob/master/scripts/chroot.sh#L171-L187 Then if host does not equal chroot architecture, copy qemu-arm-static under the chroot: https://github.com/beagleboard/image-builder/blob/master/scripts/chroot.sh#L246-L253 At which case you can chroot in... 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/CAOCHtYiTe%2B8TFkNUTsmnctS_dDZLKd4_dYR3OH%3DTVSTzFZnYPA%40mail.gmail.com.
Re: [beagleboard] building something from source in image-builder script
On Tue, Apr 27, 2021 at 12:47 PM John Allwine wrote: > > The image-builder scripts (https://github.com/beagleboard/image-builder) are > great for putting together a Beaglebone image. Is there a mechanism in there > to build specific packages from source? I see some references to qemu in > various places. Is it set up to cross compile? > > Any tips are appreciated! That what this final "target" bash script was for: https://github.com/beagleboard/image-builder/blob/master/target/chroot/beagleboard.org-buster.sh anything not packaged, etc.. Just note, qemu can be a funky beast with a mind of it's own.. 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/CAOCHtYhxydbZ2zpcOu%3D-LYiW-e5j15pdYk%3DaoTqHXE0ZD-9%2B6A%40mail.gmail.com.
Re: [beagleboard] Beaglebone AI eMMC flasher
On Mon, Apr 26, 2021 at 12:26 PM Pedro Cruz wrote: > > Hi, > > I am trying to flash BB_AI with eMMC flasher with > am57xx-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img but it aborts > flashing. > > It comes with the following error: > > Error: [/dev/mmcblk1] does not exist > > Can you help please. Please share the full boot log of the "flasher" lots of good information is dumped before it "failed".. 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/CAOCHtYhaDo6JqwsKkX7D-%3DGwtQpAr8DThBag%2B7in-H9gq%2BEL5w%40mail.gmail.com.
Re: [beagleboard] creating flasher image file from running Beaglebone
On Thu, Apr 22, 2021 at 12:42 PM John Allwine wrote: > > Thanks Robert! I issued a pull request with a couple minor changes to add a > variable where you explained: > https://github.com/RobertCNelson/boot-scripts/pull/124 > > Here's the text of the pull request that describes how it could be used to > make a smaller image size than the size of your microSD card: > > Setting the conf_rootfs_partition_size variable allows for better control > over the size of the microSD card necessary to house the resulting image when > running the beaglebone-black-make-microSD-flasher-from-eMMC.sh script. For > example, you might be working with a 32GB microSD card image, but want to > generate an image that would also fit on a 4GB microSD card, so you could do > the following: > sudo conf_rootfs_partition_size=7462912 > /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh > > Which would specify the size as 7462912 sectors, which is the size of the > eMMC rootfs partition (at least on the one I was testing on). After making > the flasher you could then use dd to get the image off the microSD card for > flashing onto other microSD cards: > > sudo dd if= of= bs=512 > count=7471104 > > 7471104 can be determined by the output from fdisk -l (one more than the End > sector, or 8192 more than the size of the rootfs partition): > Device Boot Start End Sectors Size Id Type > /dev/mmcblk0p1 * 8192 7471103 7462912 3.6G 83 Linux > > You may be able to speed up the dd command by using a bigger blocksize and > adjusting the count accordingly (using a 4MB block size): > sudo dd if= of= bs=419430 > count=912 Thanks all merged up! PS, you can add the variable to /boot/SOC.sh: https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/functions.sh#L1114 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/CAOCHtYguU_aeeN5%2BKE-X0L%2Bfmt4hJ9wCSiqa29zSS%3DTSHLwznA%40mail.gmail.com.
Re: [beagleboard] versioning beaglebone images with OSTree
On Fri, Apr 16, 2021 at 7:04 PM Robert Nelson wrote: > > On Fri, Apr 16, 2021 at 4:19 PM John Allwine wrote: > > > > I'd like to start a discussion about creating complete Beaglebone images > > that leverage OSTree to be able to atomically update the system as a whole. > > The scripts in https://github.com/beagleboard/image-builder generate > > complete images for the Beaglebone that include specific kernel, apt > > packages, boot settings, git repositories, etc. Updating a deployed > > Beaglebone without reflashing a new image involves piecemeal updating of > > those various components. Improperly updating can leave the system in a > > broken state and can be difficult to get back into a good state. It would > > be great to be able to leverage those image-builder scripts to construct > > the rootfs, add that tree as a commit to an OSTree repository and properly > > configured Beaglebones could download that commit and atomically switch to > > it to update the whole system while preserving portions of the system such > > as home directories and other key directories (/etc, /var?). If something > > did break, rolling back is easy as well. > > > > Configuring a Beaglebone this way would make most of the system read-only > > so using apt-get to install new packages wouldn't work without altering its > > implementation, but that seems like a worthy trade off. This would be for > > someone who has a Beaglebone with an out-of-the-box image and some > > scripts/servers set up in their home directory who doesn't want to worry > > too much about the system as a whole, but wants to be able to easily update > > it without reflashing or doing piecemeal updates. People who develop > > software for Beaglebones in their customers' devices could host their own > > OSTree repository and make their own modifications to the image-builder > > scripts if they have their own set of system dependencies (this is what I'd > > like to do). > > > > Does anyone else think this would be useful? Is there anyone with the > > expertise to know what details would need to be taken into account to make > > this work properly? > > > > OSTree documentation is here: https://ostreedev.github.io/ostree/ > > It lists a number of examples of it being used in various Linux > > distributions. > > I remember seeing one of Peter Robinson's demo of Fedora IoT a few > years back at ELC, that used OSTree+btrfs. It worked pretty well. At > that time, I made sure btrfs worked well for us, to possibly look down > that road. My biggest issue, the 4gb eMMC, was too limited for the > out of box images to do something like that. For an iot/console image > the idea would still work well.. While working on bullseye images > this week, i noticed we still have the "--no-merged-usr" flag for > debootstrap, we should try with that removed in 'bullseye', as ostree > needs that.. > > We did have ostree installed on the lxqt images: > > https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-lxqt-v5.4.conf#L138 > > --no-merged-usr (due to bugs in stretch/buster..) > https://github.com/beagleboard/image-builder/blob/master/scripts/debootstrap.sh#L138 bullseye and later now has --no-merged-usr disabled: https://github.com/RobertCNelson/omap-image-builder/commit/2d7bf137e3447038142a83751ed4fca76faca5fe 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/CAOCHtYgG6-42Xyr-JYVkCJ_QvQk7HTu4%2BNvpj5yGwwOJo-r6_Q%40mail.gmail.com.
Re: [beagleboard] creating flasher image file from running Beaglebone
On Thu, Apr 22, 2021 at 8:26 AM John Allwine wrote:
>
> How about changing the partition size in the make flasher script? Could there
> be an option to make it the same size as the eMMC? Where is the partition
> size determined?
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/functions.sh#L1311-L1318
LC_ALL=C sfdisk ${sfdisk_options} "${destination}" <<-__EOF__
${sfdisk_boot_startmb},,${sfdisk_fstype},*
Change to:
${sfdisk_boot_startmb},${some new var for size},${sfdisk_fstype},*
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/CAOCHtYhjisBgEExS8b23%2By2WSAfZVPQn6Koi%3D5Ffu%3D%3D%2B6qAjnQ%40mail.gmail.com.
Re: [beagleboard] creating flasher image file from running Beaglebone
On Wed, Apr 21, 2021 at 4:01 PM John Allwine wrote: > > What's the easiest way to create a Beaglebone flasher image file from a > running system? I currently use the > beaglebone-black-make-microSD-flasher-from-eMMC.sh script to directly write > to a microSD card. I then use dd to copy the microSD card to a file. I > currently only have a 32GB microSD card, though, so when I copy it the file > is 32GB. With compression that mostly goes away, but and I'd also like it to > work with smaller cards than that. Any ideas what the ideal solution is? You should be able to use gparted to shrink the partition size down, then just dd to the last sector used.. (untested in theory..) 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/CAOCHtYge9qFsN1Tq_ZzrxRyhieT_Zz%3DjUbF9SzXO4sDPxeR8Xg%40mail.gmail.com.
Re: [beagleboard] versioning beaglebone images with OSTree
On Sat, Apr 17, 2021 at 8:35 AM John Allwine wrote: > > I noticed that adding ostree to deb_includes causes problems. What’s > different about adding it to deb_additional_pkgs? So, deb_includes get directly passed to debootstrap in the first phase of debootstrap, so if it's requirements are little too complex it will fail, the deb_additional_pkgs get added during the second pass, where most of the debian initial base is already setup.. So, when adding a new package, i always add it to deb_includes first, then test.. If it fails i bump it to deb_additional_pkgs.. 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/CAOCHtYjqPfMLszkaZd%3DWZFvf2P%3DhejBuB_Sm5PdOJKetcpGs7Q%40mail.gmail.com.
Re: [beagleboard] versioning beaglebone images with OSTree
On Fri, Apr 16, 2021 at 4:19 PM John Allwine wrote: > > I'd like to start a discussion about creating complete Beaglebone images that > leverage OSTree to be able to atomically update the system as a whole. The > scripts in https://github.com/beagleboard/image-builder generate complete > images for the Beaglebone that include specific kernel, apt packages, boot > settings, git repositories, etc. Updating a deployed Beaglebone without > reflashing a new image involves piecemeal updating of those various > components. Improperly updating can leave the system in a broken state and > can be difficult to get back into a good state. It would be great to be able > to leverage those image-builder scripts to construct the rootfs, add that > tree as a commit to an OSTree repository and properly configured Beaglebones > could download that commit and atomically switch to it to update the whole > system while preserving portions of the system such as home directories and > other key directories (/etc, /var?). If something did break, rolling back is > easy as well. > > Configuring a Beaglebone this way would make most of the system read-only so > using apt-get to install new packages wouldn't work without altering its > implementation, but that seems like a worthy trade off. This would be for > someone who has a Beaglebone with an out-of-the-box image and some > scripts/servers set up in their home directory who doesn't want to worry too > much about the system as a whole, but wants to be able to easily update it > without reflashing or doing piecemeal updates. People who develop software > for Beaglebones in their customers' devices could host their own OSTree > repository and make their own modifications to the image-builder scripts if > they have their own set of system dependencies (this is what I'd like to do). > > Does anyone else think this would be useful? Is there anyone with the > expertise to know what details would need to be taken into account to make > this work properly? > > OSTree documentation is here: https://ostreedev.github.io/ostree/ > It lists a number of examples of it being used in various Linux distributions. I remember seeing one of Peter Robinson's demo of Fedora IoT a few years back at ELC, that used OSTree+btrfs. It worked pretty well. At that time, I made sure btrfs worked well for us, to possibly look down that road. My biggest issue, the 4gb eMMC, was too limited for the out of box images to do something like that. For an iot/console image the idea would still work well.. While working on bullseye images this week, i noticed we still have the "--no-merged-usr" flag for debootstrap, we should try with that removed in 'bullseye', as ostree needs that.. We did have ostree installed on the lxqt images: https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-lxqt-v5.4.conf#L138 --no-merged-usr (due to bugs in stretch/buster..) https://github.com/beagleboard/image-builder/blob/master/scripts/debootstrap.sh#L138 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/CAOCHtYgHJiESN2df7jVbUErSwL5mcoPva-woQXR91t%3D0nCJJDQ%40mail.gmail.com.
Re: [beagleboard] Re: Periodic delay reading analog inputs with C, will PRUs solve it and is it worth it?
On Fri, Apr 16, 2021 at 1:40 PM jeff@gmail.com wrote: > > Really interesting post!! > > But I can't seem to find this thread on the new Beaglebone forums webpage > over here: https://forum.beagleboard.org/ > > Am I missing something or just loosing my mind? No, the last sync of the classic BeagleBoard group ran 18 days ago. Jason is still Beta Testing the other smaller "Beagle" community sections before the main channel get's fully enabled.. Give it a few more 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/CAOCHtYh%2BJRnp73myKXbC6z6E6vUzA9x-u_%2BSeiv3y6U9_bNJdg%40mail.gmail.com.
Re: [beagleboard] What is the difference between flasher and microSD images?
On Wed, Apr 14, 2021 at 11:23 PM eb wrote: > > I'm having trouble finding information on the difference between the flasher > and microSD images. Why can an image made for microSD not be flashed to eMMC? > > The reason I'm asking is because the Debian 9.12 ImgTec image is only > available as "microSD", but I want to run this version from eMMC for > performance and reliability reasons. I also want to mount a microSD as a > different mount point for writing files. If I flash this image to eMMC, will > I run into issues? If yes, is there a way to "modify" the microSD version to > work with eMMC? There should not be any 'big' issues, i assumed most customer projects with 'qt' etc might run out of space on the eMMC.. 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/CAOCHtYjK-KVBEGGAK4t0U5tfz0Xqfod33FGV45ah7NAWRLkEqg%40mail.gmail.com.
Re: [beagleboard] Your board is connected message is not displaying in Firefox
On Tue, Apr 13, 2021 at 9:37 AM Murugesh M wrote: > > Thanks Robert Nelson. > > 1. In the getting started page, except Step 1, all other steps are not > turning to green. Still after updated the image to latest "Debian Buster IoT > Image 2020-04-06", Enabled the network connection through USB and Browsed > the beagle through 192.168.7.2 in firefox. > Attachment: DisabledSteps.png That is not used anymore.. > 2. Similarly, in the http://192.168.7.2/ide.html page, i am getting a message > "Please upgrade your software". > Attachment: Software upgrade.png > > Do i need to do some thing here to clear these two concerns? > I am little confused here. Before starting my work whether these two points > should be cleared or not. That's just an FAQ: https://beagleboard.org/upgrade showing up to upgrade things.. 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-mOLmhaCBa9dOVid_pRQdg4pa%2BvkO%3DXPMVZNMZ%2BZJ6Q%40mail.gmail.com.
Re: [beagleboard] Your board is connected message is not displaying in Firefox
On Mon, Apr 12, 2021 at 10:31 AM Murugesh M wrote: > > > Hi > I have bought a Beaglebone Black. As per the Getting started instruction, i > have connected my Beagle with Computer(Ubuntu Running) through USB. > > When i tried to launch http://192.168.7.2 in Firefox, it is NOT displaying > something like "Your board is connected! BBB SNo..." as mentioned in Getting > started page. > > Instead it is opening http://192.168.7.2/ide.html, where i can edit the > sample LED blink code available and able to run on the Beagle successfully. > > Note: I have updated the eMMC OS to latest "Debian Buster IoT Image > 2020-04-06". Even before updating this OS also, the Connected message did not > come. > > Why the Connected message is not coming for me? > Please suggest. Newer images, removed the useless getting started page.. Instead it loads up into the IDE, with a similar setup.. 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/CAOCHtYg1cuNA%2B5d5TG2Ez6xWAr209SvXYXnpXPnm4CPZqb%3DQ8Q%40mail.gmail.com.
Re: [beagleboard] Re: PRU remoteproc1 and 2 missing
On Wed, Apr 7, 2021 at 5:15 PM Cheng Chen wrote: > > Hi Dennis, > > I am following second edition. > I actually tried both 4.14 and 4.19. Either of them does not work. > But it looks like Robert's comment solves the issue. Thanks for your > suggestion though. Ah, missed that.. Yeah, it "should not have worked". ;) change: uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo to uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo in /boot/uEnv.txt If your booting 4.19.x-ti.. 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/CAOCHtYiF3w1j80n-zFNU1RxLJ%2B9bsSAbTcLLt9TOzPbQtTTqbw%40mail.gmail.com.
Re: [beagleboard] PRU remoteproc1 and 2 missing
On Wed, Apr 7, 2021 at 11:31 AM Cheng Chen wrote: > > Hi, > > I am just learning Beaglebone and have set up a Debian 10 image on a recently > purchased Beaglebone Black wireless. > I am following the Molloy's book chapter 15 to learn PRU. > However, it seems rproc module has not loaded the PRU. > Is there an additional step to allow use of the PRUs? What should I look at > to debug this issue? Thanks in advance. > > Attached is the /opt/scripts/tools/version.sh output > > git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46] > eeprom:[A335BNLTBWA51824BBWG0190] > model:[TI_AM335x_BeagleBone_Black_Wireless] > dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-2-g07d5700e21]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2016.11-rc3-2-g73df7f]:[location: dd MBR] U-Boot is too old, please run: ``` sudo apt update sudo apt install bb-u-boot-am335x-evm cd /opt/u-boot/bb-u-boot-am335x-evm/ sudo ./install.sh sudo reboot ``` > UBOOT: Booted Device-Tree:[am335x-boneblack-wireless.dts] > kernel:[4.19.94-ti-r42] Kernel is too old, please run: ``` sudo /opt/scripts/tools/update_kernel.sh ``` > pkg:[bb-cape-overlays]:[4.14.20200403.0-0rcnee0~buster+20200403 too old: ``` sudo apt install --only-upgrade bb-cape-overlays bb-customizations ``` Finally , reboot, everything should now work.. 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/CAOCHtYhzF%3D7EMCXMCJNAb_n%3De56_1_RGqmexb95K1DUkW2MDAQ%40mail.gmail.com.
Re: [beagleboard] Beaglebone Blue - pru-rproc driver not loaded - yes, I've searched here.. sorry
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo] > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] You have "2" uboot_overlay_pru defines in /boot/uEnv.txt... Disable the "AM335X-PRU-UIO-00A0.dtbo" version and reboot.. 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/CAOCHtYhAL%3DbD9xJpiJKyNEebMkTsaLiUKqvAaFv4r4%3Du8LbWtg%40mail.gmail.com.
Re: [beagleboard] Beaglebone Black Life Cycle - End of Life Plan
On Wed, Mar 31, 2021 at 11:33 AM John Zaniker wrote: > > Does anyone have any information on the plans for continued manufacturing and > support for the Beaglebone Black board? We use this board to support some > hardware development and in one of our products and we want to make sure we > plan for end of life. Thanks. There are no plans for EOL the AM335x BBB, an updated version of the pcb is in the works as some of the parts have actually gone EOL.. (microSD cage) 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/CAOCHtYhzBQyfpT%2BpzqwSkTFxShXYR8nK2ZNFwB_wMiu4MERfyw%40mail.gmail.com.
Re: [beagleboard] Overlay -- set GPIO initial value
On Thu, Mar 18, 2021 at 10:06 AM Paul Beam wrote: > > I'm creating my first device tree overlay for the PocketBeagle intending to > setup the I/O pins the way I need them without having to run an additional > script to set things up. I'm using this as a > template:https://github.com/jadonk/validation-scripts/blob/master/test-capemgr/pinctrl-test-0.dts > > Is it possible in the device tree overlay to not only set the mux setting, > but also set the pin initial value? For example, if I set a GPIO as an > output, can I also set that output hi? model it as a gpio-led, which has a default state.. https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-RELAY-4PORT-00A0.dts#L89-L92 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/CAOCHtYgA-%2BicfqONfqm3a5q%3D_MAoaSKX7mZth6jKfeKybhF5Pg%40mail.gmail.com.
Re: [beagleboard] difference between config-pin executables
On Thu, Mar 18, 2021 at 1:45 PM John Allwine wrote: > > On my Beaglebone Black, I have two config-pin executables. One is a compiled > executable from the bb-cape-overlays package, the other is a bash script in > /opt/source/bb.org-overlays: > > $ which config-pin > /usr/bin/config-pin > > $ dpkg -S /usr/bin/config-pin > bb-cape-overlays: /usr/bin/config-pin > > $ find / -name config-pin 2> /dev/null > /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin > /usr/bin/config-pin > > I have a script that configures specific pins using config-pin in the format: > config-pin P8.8 in- > Which sets pin P8.8 to an input configured as a pull down. > > The bash script seems to be the one that accepts that format, the other does > not and errors with: > ERROR: open() for /sys/devices/platform/ocp/ocp:P8_8_pinmux/state failed, No > such file or directory > > The compiled version is the default on my Beaglebone and I'd like to know > more about it. For my script to work, I need to use the other one right now. > I can certainly update the script if the compiled config-pin is a newer > version and recommended practice is to use it, but I can't seem to make it > work right. Any information is appreciated! P8.8 -> P8.08, the original had a fixup for the missing zero.. I don't think 'in-' has been migrated yet.. 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/CAOCHtYi-_7Y_XiQXzaPcMWmrzmsKB1PJ8vFyAgwcTD2Pih4okg%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 1:01 PM Robert Nelson wrote: > > On Wed, Mar 17, 2021 at 12:40 PM John Allwine wrote: > > > > The kernel doesn't seem to be the problem. Even when I change to that > > version my /dev/uio* devices aren't showing up. Am I missing a simple step > > somewhere? > > > > $ sudo /opt/scripts/tools/version.sh > > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > > 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR] > > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > > 2019.04-2-gc9b3922522]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL > > 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > > 2019.04-2-gbb4af0f50f]:[location: dd MBR] > > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts] > > UBOOT: Loaded Overlay:[BB-ADC-00A0] > > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] > > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0] > > uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo] > > Eh, I see the problem.. > > "uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo" was a recent change.. > While you have U-boot: 2019.04, it's either: Jul 08 2019 or Aug 24 > 2020, so let's fix that.. I changed this back on: https://github.com/beagleboard/image-builder/commit/442ff4a16ba2814328fa389083e1755a1bd4c9ad#diff-a085e70f4f47ad31ded59514c63774946eeda74fd30875e5abfc36073e574559 When adding u-boot overlays for am57xx devices, and adding "kernel" specific overlays, vs generic u-boot overlays.. Kernel overlays get applied first vs.. debian@bbg-pwr08-ser16:~$ ls /boot/dtbs/4.19.180-bone-rt-r61/overlays/ BBORG_FAN-A000.dtbo Generic overlays /lib/firmware/*.dtbo 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/CAOCHtYi3kEhaKhQEVqSP_S6SOrsFvNLetRTmW5gx5DYJEK0uyw%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 12:40 PM John Allwine wrote: > > The kernel doesn't seem to be the problem. Even when I change to that version > my /dev/uio* devices aren't showing up. Am I missing a simple step somewhere? > > $ sudo /opt/scripts/tools/version.sh > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-2-gc9b3922522]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL > 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2019.04-2-gbb4af0f50f]:[location: dd MBR] > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts] > UBOOT: Loaded Overlay:[BB-ADC-00A0] > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0] > uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo] Eh, I see the problem.. "uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo" was a recent change.. While you have U-boot: 2019.04, it's either: Jul 08 2019 or Aug 24 2020, so let's fix that.. sudo apt update sudo apt install bb-u-boot-am335x-evm Then: cd /opt/u-boot/bb-u-boot-am335x-evm/ sudo ./install.sh sudo reboot Then you should see the uio node here: UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts] UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0] UBOOT: Loaded Overlay:[BB-ADC-00A0] UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] 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/CAOCHtYjjJt-f%3DKF2Thg02UnFttLFXehZ8dgGvGyW97LSF7KoVg%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 12:17 PM John Allwine wrote: > > I tried a different kernel, one that I know works with uio_pruss because I'm > using it on a different image (4.19.59-bone-rt-r36). In my custom image, > though, the /dev/uio* devices aren't showing up. Here's version.sh output on > it: > > git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0] > eeprom:[A335BNLT000C1626BBBG0552] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Pocket NC Debian Buster Image 2021-02-01] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL > 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.04-2-gc9b3922522]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL > 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2019.04-2-gbb4af0f50f]:[location: dd MBR] > UBOOT: Loaded Overlay:[BB-ADC-00A0] > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0] > kernel:[4.19.59-bone-rt-r36] probably fixed, between r36 and r61... http://gfnd.rcn-ee.org:81/farm/uptime/pwr08-ser16-bbg-4.19.180-bone-rt-r61.log kernel:[4.19.180-bone-rt-r61] ls /dev/uio* -la crw-rw 1 root users 240, 0 Mar 16 15:10 /dev/uio0 crw-rw 1 root users 240, 1 Mar 16 15:10 /dev/uio1 crw-rw 1 root users 240, 2 Mar 16 15:10 /dev/uio2 crw-rw 1 root users 240, 3 Mar 16 15:10 /dev/uio3 crw-rw 1 root users 240, 4 Mar 16 15:10 /dev/uio4 crw-rw 1 root users 240, 5 Mar 16 15:10 /dev/uio5 crw-rw 1 root users 240, 6 Mar 16 15:10 /dev/uio6 crw-rw 1 root users 240, 7 Mar 16 15:10 /dev/uio7 ( we need to change that to root:gpio...) 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/CAOCHtYgU252vMO3pxq%3DV5bbN0Kzdg2z-jmk%2Bznc1E3CDrr%3DHrw%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 11:24 AM John Allwine wrote: > > How about the rt kernel? I'm using 4.19.94-ti-rt-r57 and don't seem to have > the /dev/uio* devices. Is there something else I need to activate those > devices or does the rt kernel not support uio_pruss? sudo /opt/scripts/tools/version.sh 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/CAOCHtYhP359QSK0P8ZJmupNqJ0Ap870jOgbQdYVPQHcncEqxxA%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 10:46 AM John Allwine wrote: > > Great, and so if I had used one of those --enable-uboot-pru* options and I > wanted to manually change an image to using uio_pruss, is it just a matter of > changing /boot/uEnv.txt to use that overlay? Correct, 4.14.x-ti & 4.19.x-ti kernels support changing the pru driver from /boot/uEnv.txt.. Just un-comment the version you want.. 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/CAOCHtYgrETMrZjb_QUBS5WSRRCz38KOkD64TR3sTcU%2BDCVnb7A%40mail.gmail.com.
Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts
On Wed, Mar 17, 2021 at 10:33 AM John Allwine wrote: > > What is necessary to set up a Beaglebone Black image with uio_pruss enabled > rather than remoteproc? > > If I wanted to build an image using this config file, for example: > https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-console-v4.19.conf > > What steps would I have to take? When you run "setup_sdcard.sh" to generate your target *.img or microsd, just don't pass any "--enable-uboot-pru*" options.. https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L2070-L2084 as the default is: uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L1303-L1348 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/CAOCHtYhYkAMPoOimtmJ2_nmCYeHQNr90SakpS4KRUC7T8r9H3g%40mail.gmail.com.
Re: [beagleboard] Re: Beaglebone Black upgrade error messages
On Tue, Mar 16, 2021 at 9:59 AM KenUnix wrote: > > set_ > > Hi. As I said I'm not using email. If there is another reason to use nginx > let me know. nginx is a webserver, it replaced apache in our default image about a year ago, as it's easier to proxy cloud9/node-red/etc. ;) 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/CAOCHtYjAwcCqY56pveTJQcfwbhEYE1H_VxNXusGmjsX%3DE_%2BNEg%40mail.gmail.com.
Re: [beagleboard] Micron MT41K256M16HA-125:E
On Thu, Mar 11, 2021 at 7:32 AM Micka wrote: > > Hi, We have to change the component: Micron MT41K256M16HA-125:E > > This list: > > Micron MT41K256M16TW-107:P > Kingston D2516EC4BXGGB > Kingston D2516EC4BXGGB-U > > are all compatible ? without any change in the configuration? > No change to the software stack with those: https://github.com/beagleboard/beaglebone-black/blob/master/BBB_BOM.csv PS, BeagleBoard.org boards have been using Kingston memory/eMMC for a few years now... 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/CAOCHtYhRcBOgce-BXbuPQRs9%3D5ttcmyWHVPEHAKcoWKZGLWR6A%40mail.gmail.com.
Re: [beagleboard] BBAI use SDCard for extra storage
On Mon, Mar 8, 2021 at 8:40 PM Chinmay Pendharkar wrote: > > Hello people, > > I'm trying to use the SDCard on the BBAI for extra storage. > > - I have successfully flashed Debian Console image onto the EMMC using the > published flasher images. > - Next, I formatted a new microSD Card with MBR and create a FAT partition > - Next, I created a uEnv.txt in that partition with the contents > > ``` > mmcdev=1 > bootpart=1:2 > mmcroot=/dev/mmcblk1p2 ro > optargs=quiet > ``` > I was using this article as a reference : > https://elinux.org/Beagleboard:MicroSD_As_Extra_Storage > > However, when I insert the microSD card and reset the board, I don't see > anything on the serial console. > > Usually, I can see > > ``` > U-Boot 2020.10-rc1-1-gc5bc0aaa70... > ... > > but when I have this microSD card inserted, I don't see anything. > > What am I doing wrong? On the BBAI, if you want to use the microSD as extra storage, do NOT create any files named "uEnv.txt" under /, or /boot/ , etc.. Then u-boot will happily ignore it.. The BBAI (am57xx) has a different boot order then the BBB (am335x), on the BBAI the microSD is always first, where as the BBB the eMMC is first.. 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/CAOCHtYhBypCOsHFUB9YHfrdwHDQfc7ZyT930s_U2LjQvrnU_NA%40mail.gmail.com.
Re: [beagleboard] BBB boots kernel from SD card but uses distro from EMMC after kernel upgrade
On Mon, Mar 8, 2021 at 4:40 PM Nuno Gonçalves wrote: > > > > On Friday, October 2, 2020 at 3:17:51 PM UTC+2 RobertCNelson wrote: >> >> > [ 0.00] Linux version 5.9.0-rc7-bone4.1 (sleepy@seraph) >> > (arm-none-linux-gnueabihf-gcc (GNU Toolchain for the A-profile >> > Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 2019100 >> >> Yay 5.9 boots. ;) >> >> > [ 5.242340] mmc0: new high speed MMC card at address 0001 >> > [ 5.251694] mmcblk0: mmc0:0001 M62704 3.56 GiB >> > [ 5.258406] mmcblk0boot0: mmc0:0001 M62704 partition 1 2.00 MiB >> > [ 5.266465] mmcblk0boot1: mmc0:0001 M62704 partition 2 2.00 MiB >> >> Wait a minute.. that's the eMMC... >> >> > [ 6.457532] mmc1: new high speed SDXC card at address >> > [ 6.466835] mmcblk1: mmc1: SN64G 59.5 GiB >> > [ 6.478915] mmcblk1: p1 >> >> There's your microSD card.. >> >> Uhoh.. They swapped... That's a regression.. >> > > Hi Robert, > > v5.10.21 still have the eMMC as mmc0. Is this really a regression or going > forward they are keeping it? Grab this: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/commit/?h=for-next&id=9bbce32a20d6a72c767a7f85fd6127babd1410ac 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/CAOCHtYisBrbUk0xH-gzQ6rki1oz1nemPtKV1Bdbw_DHEAoZaag%40mail.gmail.com.
Re: [beagleboard] "Could not initialize egl display" when starting a Qt application
On Mon, Mar 1, 2021 at 10:02 AM eb wrote:
>
> Hi all! I've spent a few days trying to get an LCD screen working with
> hardware acceleration, eglfs, on my Beaglebone Black Wireless. My end goal is
> running a PyQT5 application. After reading some discussions here, I found
> that the Stretch ImgTec Beaglebone image already has opengl and sgx
> dependencies installed. After installing that image on my SD and trying to
> start the test dashboard application as explained here, it just says:
>
> Could not initialize egl display
> Aborted
>
> I know that my display is working as it displays a login screen in the
> terminal with tty1, AND it shows a basic pyqt5 application using linuxfb
> on the screen with the command `python3 test.py -platform linuxfb`.
>
> If I use qt debug variables, it still doesn't show any errors
>
> cd /usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard
> export QT_LOGGING_RULES=*=true
> export QSG_INFO=1
> export QT_QPA_EGLFS_DEBUG=1
> export QT_DEBUG_PLUGINS=1
> export QT_QPA_PLATFORM=eglfs
> export QT_QPA_EGLFS_INTEGRATION=none
> ./dashboard
>
> Extracted output (to keep it short):
>
> Got keys from plugin meta data ("eglfs")
> Got keys from plugin meta data ("linuxfb")
> Got keys from plugin meta data ("minimal")
> Got keys from plugin meta data ("minimalegl")
> Got keys from plugin meta data ("offscreen")
> Got keys from plugin meta data ("xcb")
> loaded library
> "/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqeglfs.so"
> Got keys from plugin meta data ("eglfs_kms_egldevice")
> Got keys from plugin meta data ("eglfs_kms")
> Got keys from plugin meta data ("eglfs_x11")
> QFactoryLoader::QFactoryLoader() checking directory path
> "/usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard/egldeviceintegrations"
> ...
> qt.qpa.egldeviceintegration: EGL device integration plugin keys:
> ("eglfs_kms_egldevice", "eglfs_kms", "eglfs_x11")
> qt.qpa.egldeviceintegration: Using base device integration
> Could not initialize egl display
> Aborted
>
> I don't think an X server is running (searched via `ps aux | grep -i x`).
Correct no x server..
>
> I also tried using Buster image without graphics and followed the instruction
> in the wiki page listed above, but still no dice. Does anyone have any
> pointers on how to continue with this?
Imagination wrote a fun with beagle, which helps explain the stretch
imgtec image and egl, etc..
https://university.imgtec.com/fun-with-beagle-gpu/
That ^ might help debug what's wrong..
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/CAOCHtYhHL%2BbrLn4kF8-pjq%2BuPA7XjW3MgnV07A-CKWaXpVh0uw%40mail.gmail.com.
Re: [beagleboard] How to change default ssid and password of wifi i.e. "BeagleBone-xxxx" and "BeagleBone"
On Sun, Feb 28, 2021 at 10:49 AM Steen Bløndal wrote: > > Hi, > > You are right, - I have tested it and it works fine when using > "BatteryCharger" as password instead of "BeagleBone". Thanks for testing, i've documented this for the next user: ;) https://github.com/RobertCNelson/bb-wl18xx-firmware/commit/e6aa38f16e836de484227e537029e17b07c3d92f 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/CAOCHtYg880d_kyW95mwenznnxYw7Z6TxBtNAaHc%2BMRkNF%3DOMFA%40mail.gmail.com.
Re: [beagleboard] How to change default ssid and password of wifi i.e. "BeagleBone-xxxx" and "BeagleBone"
On Sun, Feb 28, 2021 at 10:07 AM Steen Bløndal wrote:
>
> Hi Robert,
>
> I am not using any special characters in the password, see attached.
> I think there is a dependency somewhere requiring the "BeagleBone" password
> to work.
> My setup is up to date including kernel. If you want me to test anything just
> let me know.
Because of our configuration:
wpa=2
wpa_passphrase=${wifi_password}
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
I think your 3 character password is just too short.. It looks like
we need a minimum of 8 characters for ^ configuration..
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/CAOCHtYh3uv0xzWQ6iX2uD89K09-TJ4Pg%2B6qGD%3DViUY_1tQWc0Q%40mail.gmail.com.
Re: [beagleboard] How to change default ssid and password of wifi i.e. "BeagleBone-xxxx" and "BeagleBone"
On Sun, Feb 28, 2021 at 5:26 AM Stein wrote: > > Hi > There is an issue with BeagleBone AI, bb-wl18xx. > When modifieng the USE_PERSONAL_PASSWORD to anything but "BeagleBone" it > stop working. The device is not visable any more. > Changing USE_PERSONAL_PASSWORD back to "BeagleBone" then everything is fine > again. > Does anyone know how to get around this? That variable is used like this: https://github.com/rcn-ee/repos/blob/master/bb-bbai-firmware/suite/bionic/debian/bb-bbai-tether#L53 Without sharing your "personal" passwords.. Are you using any special characters? That might break my how i utilize the wifi_password variable in that script.. If you want, please randomize your password, but have those same special chargers, and i'll test it out locally.. 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/CAOCHtYgvSA8SztyW3LocON1GJ4kPxoA%3Dk8vrqT008aNteVEvuw%40mail.gmail.com.
Re: [beagleboard] bb-usb-gadgets and default gateway on BBB
On Thu, Feb 25, 2021 at 11:50 PM Jake Danczyk wrote: > > On the Beaglebone Black, after installing the latest bb-usb-gadgets, it seems > that the dhcp default gateway has changed, and the new default isn't allowing > network access over ethernet. I've poked around looking for relevant config > files but haven't found the right ones yet. > > Running "ip route show" now gives: > > >default via 192.168.7.1 dev usb0 onlink > >192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.97 > >192.168.2.1 dev eth0 scope link > >192.168.6.0/24 dev usb1 proto kernel scope link src 192.168.6.2 > >192.168.7.0/30 dev usb0 proto kernel scope link src 192.168.7.2 > > When the 192.168.7.1 gateway is deleted (sudo route del default gw > 192.168.7.1), the 192.168.2.1 dev eth0 route becomes default and I have > internet connection. After reboot, 192.168.7.1 is default again. Hi Jake, There really shouldn't be a major change with that package, it was mostly a copy and paste from the boot script to something more maintainable.. https://github.com/beagleboard/customizations/tree/master/usr/bin 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/CAOCHtYgpy1zkiS-Yotiyp0Qp240PY9pM9v0%2BoiQLi-OSPBGA3w%40mail.gmail.com.
Re: [beagleboard] Can't get into BeagleBone Black's SSH via my Mac
On Thu, Feb 25, 2021 at 8:13 AM Riggs Markham wrote: > > I have a Windows 10 desktop computer that I've been working on for years, and > I got a new BBB in January and flashed it with the latest image and it's been > working fine on there, no drivers needed as far as I remember. Been able to > ssh in via the USB connection and it seems to work great. > But I just got a new MacBook Air (which came with Big Sur 11.2.1), and I'd > like to be able to use it on there. I've been trying to install the drivers > on the getting started page, but neither works. The serial one (HoRNDIS, > which is I think the one I need) keeps telling me it won't work on this > version of my computer. I can't ssh in to either *6.2 or *7.2 and the Network > tab of my system preferences seems to think that the cable is unplugged (it's > not). > I'm hesitant to reflash my BBB as I've been doing some solid stuff on there > and don't want to lose it. > What can I do? Am I screwed w/o refreshing my BBB or rolling back my Mac > version (not happening)? It won't be the end of the world if I can't use it > with my Mac, but it'd certainly be nice if I could. > Thanks in advance. This was fixed shortly after release .. BigSur removed support for ecm, so we swapped to ncm.. https://github.com/RobertCNelson/boot-scripts/commit/b61125c1485bee929340cacc06c85c6fcfd678bc#diff-37b07cb09a69a3f886bdc703e8d66695b328c840450e055d70c3e0f1af793e8c Just grab one of the latest testing images.. ;) https://rcn-ee.net/rootfs/bb.org/testing/2021-02-22/ 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/CAOCHtYjP5T1U8RNM3Gz6__i40sJy0XDV4nOs7LtLFO_06BQjEQ%40mail.gmail.com.
Re: [beagleboard] Re: HELP : pocketbeagle UART issue using node js
On Wed, Feb 24, 2021 at 11:08 AM Piyush Raj ae19m009
wrote:
>
> I tried suppressing the error produced by line 462 by bruteforce (putting
> is_capemgr as True). and got rid of this error.
> however, got stuck with the error in 468 (Device Tree overlay fragment
> BB-UART4 not loaded).
> which means that load_dt fails to fetch the port. i am trying to find out
> location of load_dt function. hopeful to solve this issue with community
> help. thanks
load_dt is a relic from kernel overlays.. Just make sure you loaded
the BB-UART4 u-boot overlays and nuke your "var b =
require('bonescript');" as it's not supported/needed/required
anymore..
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/CAOCHtYjQT%2Btu1yaws8Ph6yCgdwg-udc1CNJutU7PfcuXuxFwPg%40mail.gmail.com.
Re: [beagleboard] the way to set MMC mode(8-bit transfer) and 384Mbps at BBBW
On Tue, Feb 23, 2021 at 5:59 PM ha ppay wrote: > > Hi RobertCNelson, > > I recently knew that the SD card was just one type of MMC, but I just made a > mistake. Thank you for your advice. > yes, I knew that the am335x MMCHS supports up to 4-bit mode on SD cards. PS you can cat the debugfs to find out what mode this is in: MicroSD: 4-bit mode debian@bbb-pwr01-ser09:~$ sudo cat /sys/kernel/debug/mmc0/ios clock: 5000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 2 (4 bits) timing spec: 2 (sd high-speed) signal voltage: 0 (3.30 V) driver type: 0 (driver type B) eMMC: 8-bit mode debian@bbb-pwr01-ser09:~$ sudo cat /sys/kernel/debug/mmc1/ios clock: 5200 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 3 (8 bits) timing spec: 1 (mmc high-speed) signal voltage: 0 (3.30 V) driver type: 0 (driver type B) If you can't read that, then update your fstab: debian@bbb-pwr01-ser09:~$ cat /etc/fstab | grep debug debugfs /sys/kernel/debug debugfs mode=755,uid=root,gid=gpio,defaults 0 0 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/CAOCHtYgoybBP5q1yg4emeV0_%2BBN3S0i2_oN%3D7SAwC91SS4NLKA%40mail.gmail.com.
Re: [beagleboard] the way to set MMC mode(8-bit transfer) and 384Mbps at BBBW
On Tue, Feb 23, 2021 at 5:40 PM ha ppay wrote: > > Hi, > I forgot attaching kernel log. > I don't know if I can add it by replying to the comment, but I will challenge > it. > I thought that the SDHC/MMC are type of media, and "high speed" indicates > 4-bit mode. > [1.086202] mmc0: new high speed SDHC card at address 0001 > [1.091531] mmcblk0: mmc0:0001 ASTC 29.0 GiB > > [1.118517] mmc1: new high speed MMC card at address 0001 > [1.123897] mmcblk1: mmc1:0001 M62704 3.56 GiB "NO"... "high speed" doesn't mean anything on "bit-ness".. https://elixir.bootlin.com/linux/v5.11/source/drivers/mmc/core/bus.c#L366 https://elixir.bootlin.com/linux/v5.11/source/include/linux/mmc/host.h#L575 So it's stuck in MMC_TIMING_SD_HS/MMC_TIMING_MMC_HS timings.. You don't get SDR12/DDR50 mode till mmc_card_uhs and then it would say: [1.086202] mmc0: new ultra high speed SDHC card at address 0001 either way, your eMMC is still in 8-bit mode.. BUS width just changes how the data is communicated.. https://elixir.bootlin.com/linux/v5.11/C/ident/MMC_BUS_WIDTH_8 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/CAOCHtYh%2BoBck4bXmrFG3ziR6W-51HGPbyHr59KXT8CZii-pVYg%40mail.gmail.com.
Re: [beagleboard] the way to set MMC mode(8-bit transfer) and 384Mbps at BBBW
On Mon, Feb 22, 2021 at 8:34 PM ha ppay wrote:
>
> Hi RobertCNelson,
>
> Thank you for checking the relevant part.
> the description of the Device tree is as follows. Is this overwriting the
> setting? In fact, when I set this part to
> bus-width = <0x08>
> , the Boot time did not change much.
> Could you tell me if there is a way to check the current transfer bit mode?
>
>
> mmc@4806 {
>compatible = "ti,omap4-hsmmc";
>ti,hwmods = "mmc1";
>ti,dual-volt;
>ti,needs-special-reset;
>ti,needs-special-hs-handling;
>dmas = < 0x2d 0x18 0x00 0x00 0x2d 0x19 0x00 0x00 >;
>dma-names = "tx\0rx";
>interrupts = < 0x40 >;
>reg = < 0x4806 0x1000 >;
>status = "okay";
>bus-width = < 0x04 >;<===
>pinctrl-names = "default";
>pinctrl-0 = < 0x2e >;
>cd-gpios = < 0x2f 0x06 0x01 >;
>vmmc-supply = < 0x30 >;
>phandle = < 0x288 >;
> };
Well, mmc@4806 -> is the microSD on the BBBW -> which only has 4
data wires hooked up...
So, yeah, that won't change the eMMC..
PS, the factory default eMMC on these boards isn't known for speed,
the version used is more for reliability..
You can buy pretty cheap fast microSD on a 4-bit bus that will outpace
the factory default eMMC on a 8-bit bus..
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/CAOCHtYivJYXQnYQgmRUm5LV37D6jpSUhuLZtXcwJ7t_ySERURA%40mail.gmail.com.
Re: [beagleboard] the way to set MMC mode(8-bit transfer) and 384Mbps at BBBW
On Thu, Feb 18, 2021 at 1:10 AM ha ppay wrote:
>
>
> Hi Everyone.
> I'm collecting information to get even faster boot times,
> I have 2 questions.
> It is written that it is possible to boot from MMC (8bit mode) (18.1.1 MMCHS
> Features) using MMC mode with TRM of am335x.
> - Clock support
> -96-MHz functional clock source input
> -up to 384Mbit/sec (48MByte/sec) in MMC mode 8-bit data transfer
> -up to 192Mbit/sec (24MByte/sec) in High-Speed SD mode 4-bit data transfer
> -up to 24Mbit/sec (3MByte/sec) in Default SD mode 1-bit data transfer
>
> Also, the SD_CON register DW8 Field has a flag for it.
> I expect this setting to start up much faster.
> In BBB, how do I set it to 8bit mode and how do I set the frequency to
> 384Mbit / sec (is it mmc_clk/clock-div in Devicetree?)?
It's already in 8-bit mode..
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-boneblack-common.dtsi#n23
&mmc2 {
vmmc-supply = <&vmmcsd_fixed>;
pinctrl-names = "default";
pinctrl-0 = <&emmc_pins>;
bus-width = <8>;
status = "okay";
non-removable;
};
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/CAOCHtYhuU-P8JNE45CudLK2TUn3-ZW0ePhfZx_p%2BH7i0HGzuUw%40mail.gmail.com.
Re: [beagleboard] Upgrading Beagleboard Blacks from Debian 9.5 => Debian 10.x?
On Sat, Feb 20, 2021, 2:44 PM Robert Heller wrote: > At Sat, 20 Feb 2021 08:16:29 -0600 Robert Nelson > wrote: > > > > > Content-Type: text/plain > > > > Content-Type: text/plain > > > > On Sat, Feb 20, 2021 at 7:34 AM Robert Heller > wrote: > > > > > > Is it possible to upgrade Beagleboard Blacks from Debian 9.5 => Debian > 10.x > > > using apt? Eg editing /etc/apt/sources replacing stretch with buster > and > > > running apt update / apt full-upgrade? Are there any gotchas I need > to watch > > > out for? I have 32G microSD cards with some local software and > various local > > > configs and would rather not just download an image and redo all of > that > > > unless I really have to. > > > > editing stretch -> buster should be fine.. > > > > just upgrade apt/dpkg first, rerun update, then do the upgrade, then > > dist-upgrade... > > OK, I did this on my two BeagleBone Blacks. Everything updated, except > they > are still using thier older (4.x) kernels. I take it I need to do some > additional things to update the kernel? I have a RPi 4 with an recent > Raspbian image (Debian 10 [buster] based) running a 5.x series kernal, so > I > expected a newer kernel. So I'd like to update the kernel (unless there > is > some reason I shouldn't). Install whatever branch you want. We don't force one global option.. https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Mainline_.285.4.x_lts.29 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/CAOCHtYitHsP9WGcHAa9u93bdfHCqSAehaGgzyQSEp9iRyvHtPg%40mail.gmail.com.
Re: [beagleboard] Upgrading Beagleboard Blacks from Debian 9.5 => Debian 10.x?
On Sat, Feb 20, 2021 at 7:34 AM Robert Heller wrote: > > Is it possible to upgrade Beagleboard Blacks from Debian 9.5 => Debian 10.x > using apt? Eg editing /etc/apt/sources replacing stretch with buster and > running apt update / apt full-upgrade? Are there any gotchas I need to watch > out for? I have 32G microSD cards with some local software and various local > configs and would rather not just download an image and redo all of that > unless I really have to. editing stretch -> buster should be fine.. just upgrade apt/dpkg first, rerun update, then do the upgrade, then dist-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/CAOCHtYgkeHnORY7OW5tnq%2BN185_QYe%2BnQsxbDT7dPU_MV0nbvw%40mail.gmail.com.
Re: [beagleboard] am335x_evm.sh
Hi Paul, Thanks for the testing and verification! ;) I'd love to refactor and clean up this script. Sadly it's supporting 3.8.x -> 5.10.x based linux kernel's! On Tue, Feb 16, 2021 at 3:26 PM Paul Beam wrote: > > Like others, I have sought to reduce boot time on the PocketBeagle, and I > have run into a few questions that maybe only Robert can answer. > > First of all, this line appears to be wrong: > > echo CD > os_desc/b_vendor_code > > It gives me this error: > > Feb 17 21:02:36 V2-2 sh[203]: sh: echo: I/O error This was either for 4.4.x/4.9.x era, i think for 4.14.x it's actually set in driver by default.. > > I added a bunch of echo statements to narrow down which line was generating > this, and I'm pretty sure this is it. It is the section that sets the > Windows 10 attributes. > > The bigger issue is the time this script takes to run. I'm booting in a tad > under 40 seconds, and this script is the bulk of it. I have narrowed down > the offending section to this line: > > systemctl restart dnsmasq || true > > The log with my additional comments looks like this: > > Feb 17 21:02:38 V2-2 sh[203]: am335x_evm: Starting usb1 network > Feb 17 21:02:38 V2-2 sh[203]: am335x_evm: Setting up dnsmasq > Feb 17 21:02:39 V2-2 sh[203]: Stopping udhcpd (via systemctl): udhcpd.service. > Feb 17 21:02:39 V2-2 sh[203]: am335x_evm: dnsmasq: setting up for usb0/usb1 > Feb 17 21:02:39 V2-2 sh[203]: am335x_evm: disable_connman_dnsproxy > Feb 17 21:02:39 V2-2 sh[203]: am335x_evm: finished disable_connman_dnsproxy > Feb 17 21:02:39 V2-2 sh[203]: am335x_evm: Restarting dnsmasq > Feb 17 21:03:06 V2-2 sh[203]: am335x_evm: LOG: dnsmasq is disabled in this > scrip So dnsmasq is fun. It doesn't deal with dynamic devices usb0/usb1 & SoftAp0 in a nice way.. If it is started before usb0/usb1/etc exists it'll just exit out. I'd love to find a way to trigger it'start after usb0/usb1 is configured.. Just had a thought, does forking that process help? https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L764 systemctl restart dnsmasq || true -> systemctl restart dnsmasq & || true ??? > Now, I have just been going through the script trying to eliminate most of > the hardware tests since my board is fixed, and deleting what I don't think I > need. But there are some things that confuse me. This script disables both > udhcpd and dnsmasq. Why not just not auto-start those services or set them > to start when this script is complete? This script also seems to touch some > things that affect hostapd. So udhcpd only supports one interface.. usb0, we've long switched to dhsmasq, so it's more convenient to get udhcp out of the way.. hostapd is only for the wifi devices, it also requires dnsmasq up and running.. > Is there any description on how this script interacts with other systemd > services? It clearly does some necessary things as disabling it does not > improve my boot performance, and the combination clearly gives a brilliant > "out of the box" experience for someone just starting out. The combination, > however, is a bit confusing when it comes to fine tuning. PS, if you nuke the initrd sudo rm /boot/initrd.img-* you'll get another boot speed up.. 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/CAOCHtYgbburF8NOMeLasaUb1KkWhtzRmAa%3DviA%3Dw1YBEwcbD1g%40mail.gmail.com.
Re: [beagleboard] Re: BBB Core Temperature
On Sun, Feb 14, 2021 at 12:10 PM Georg Gast wrote: > > On an image from 2014 it is located on > "/sys/devices/ocp.3/44e10448.bandgap/temp1_input". Its kernel 3.8.13-bone50 > and the dogtag is: "BeagleBoard.org BeagleBone Debian Image 2014-05-14" > > Maybe i can investigate the dts and find whats the driver. TI's hardware team decided to not mainline that subsystem as it was un-reliable.. it was only ever in the 3.8.x branch, consider the driver broken. 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/CAOCHtYjLLx3URjNjVsVzJDTQEsDbVKLFUjMvPLDoD31JqA1iNg%40mail.gmail.com.
Re: [beagleboard] Boot on power BB-x15
On Tue, Feb 9, 2021 at 11:13 AM Joseph Tarnow wrote: > > Howdy dudes and dudettes, > > I have a Beagleboard x15, and I am trying to make it boot on power, so if I > lose power the board will start when power resumes. I found this thread, but > couldn't make sense of it. Perhaps my google foo is bad, but I couldn't find > anything else. Does anyone know how to do this? Here's a quick answer.. Users debugging with JTAG have the same issue as above.. So look at your board, find J5, then proceed to solder the two holes together with a wire.. But here's the warning.. If you boot with a blank eMMC and a blank microSD, so U-BOOT does NOT LOAD... Given enough time with this situation you will destroy the AM57xx and it'll never boot again... 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/CAOCHtYit67Q1%3Dd9U6X%2BF-K%3DVWdi9cb3QqEuoKu2Ord_yrH5meQ%40mail.gmail.com.
Re: [beagleboard] BBAI Stuck Clock Frequency
On Tue, Feb 9, 2021 at 9:53 AM stephen@gmail.com < stephen.nguye...@gmail.com> wrote: > [image: BBAIThermals.png] > It seems normal. the cpu is 58.5C, thus it's in state 3... (3.5 degrees C over passive limit)... If you stick a fan on it or blow across it, it'll auto upclock.. 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/CAOCHtYgnDYm6qpcBgWTt44diXOnh8t5KJa9HtJuteMarYYPf6Q%40mail.gmail.com.
Re: [beagleboard] BBAI Stuck Clock Frequency
On Tue, Feb 9, 2021 at 8:59 AM stephen@gmail.com wrote: > > Why is my device only limited to 400 MHz? > > It doesn't change no matter what I do Check the temps: /opt/scripts/device/x15/test_thermal.sh Do you have an external fan to blow on it? 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/CAOCHtYhUGzvQBanw5G4AcQF%2BWnEDj2egTU6vs1YyB%3DXsVRBNAQ%40mail.gmail.com.
Re: [beagleboard] Grove Base Cape for BeagleBone(R) v2.0 disables BBB ethernet
On Sun, Feb 7, 2021 at 7:03 AM Chris Green wrote: > > I have an old[ish] BBB on which I have been doing some experimenting > for a friend. I have the current Debian 10 console version installed. > > One of the things to try was to install a Grove cape, one of these:- > > https://www.seeedstudio.com/Grove-Base-Cape-for-Beagleboner-v2-0.html > > It seems to completely disable all ethernet, neither the RJ-45 nor the > ethernet over USB works. Is this to be expected? > > The BBB's ethernet works fine when the cape is removed again, but > having no way to communicate with it when the cape is attached makes > it rather difficult to do anything. Uh, no... with it plugged in please run.. sudo /opt/scripts/tools/version.s 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/CAOCHtYjhOC208Mv0dq8XLOZeTS-TgfqkvqjfKh1%2BFcfZEc7PiQ%40mail.gmail.com.
Re: [beagleboard] Re: Debugging SPI device
On Sat, Feb 6, 2021 at 7:22 PM Yendor wrote: > > Thanks for the info Robert, would you know how I could reclaim / rewrite > these pins to act as SPI pins? > > What would be the best way of doing this? modify > 'am335x-bonegreen-wireless-uboot-univ.dts' or can we get the boards to load a > custom default dt config? Honestly, since you have a custom board, i'd just start carving a new *.dtb and stop using overlays for other boards.. 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/CAOCHtYi9Bxw80givWRrsHs42Ab_gSNWbymu45wPmkBgjhexh4w%40mail.gmail.com.
Re: [beagleboard] Re: BBB emmc booting and SPI0 nor flash
On Sun, Feb 7, 2021 at 6:12 AM JeongHwan Kim
wrote:
>
> I found the pinmux state is differnet between the emmc boot and sd card boot.
> I set the spi0 pins (/ce, sclk, d1, d0) with MODE0 in am335x-bone-common.dtsi.
> When the board runs in sd card boot, the spi0 pins mode is MODE 0.
> but in emmc boot, the spi0 pins mode is MODE 7.
> So, in emmc boot mode, I cannot access to spi-nor flash.
>
> I set the pin mux state in am335x0-bone-common.dtsi like this:
>
>
>
> spi0_pins: spi0_pins {
> pinctrl-single,pins = <
> AM33XX_PADCONF(AM335X_PIN_SPI0_SCLK, PIN_INPUT_PULLUP, MUX_MODE0)
> AM33XX_PADCONF(AM335X_PIN_SPI0_D0, PIN_INPUT_PULLUP, MUX_MODE0)
> AM33XX_PADCONF(AM335X_PIN_SPI0_D1, PIN_OUTPUT_PULLUP, MUX_MODE0)
> AM33XX_PADCONF(AM335X_PIN_SPI0_CS0, PIN_OUTPUT_PULLUP, MUX_MODE0)
> >;
> };
> ...
>
> &spi0 {
> pinctrl-name = "default";
> pinctrl-0 = <&spi0_pins>;
> status = "okay";
>
> spi-flash@0 {
> #address-cells = <0x1>;
> #size-cells = <0x1>;
> compatible = "jedec,spi-nor";
> reg = <0x0>;
> spi-max-frequency = <50>;
> partition@0 {
> label = "partition1";
> reg = <0x0 0x1>;
> };
> partition@20 {
> label = "partition2";
> reg = <0x1 0x1>;
> };
> };
> };
>
> I don't know why the pin mode state is different between the emmc and sd card
> boot mode.
> Is there any factor to effect for the spi0 pins mode to differ beween emmc
> and sd card boot?
I'm betting your version of u-boot on the eMMC and microsd are different..
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/CAOCHtYiCCfeAo93Mz7cOhuQz%3DEQLeO7WNT%3DGMXa%2BVXqOdHT__A%40mail.gmail.com.
Re: [beagleboard] Re: Debugging SPI device
On Sat, Feb 6, 2021 at 4:03 PM Yendor wrote: > > Digging down, it looks like 'am335x-bonegreen-wireless-uboot-univ.dts' is > been loaded as the default and this includes > 'am335x-bonegreen-wireless-common-univ.dtsi' > which in turn sets 'MCASP0_ACLKX' and 'MCASP0_FSX' as 'audio' on the P9 > header. > > Question is it possible to modify 'am335x-bonegreen-wireless-uboot-univ.dts' > to allow me to use SPI1 on the pins I want? > > The pins I need are: > ZCZ BallPin NameSignal ModeAssumed Commands > A13 MCASP0_ACLKXSPI1_SCLK 3 AM33XX_IOPAD(0x0990, > PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE3) > B13 MCASP0_FSX SPI1_D0 3 AM33XX_IOPAD(0x0994, > PIN_INPUT_PULLUP | INPUT_EN | MUX_MODE3) > D12 MCASP0_AXR0 SPI1_D1 3 AM33XX_IOPAD(0x0998, > PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE3) > V17 GPMC_A11LoRa_CS17 AM33XX_IOPAD(0x086c, > PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE7) > > Is anyone able to show me what would need to be modified, Thanks. > That's right, the BBGW, has the audio muxed to the wl18xx's bluetooth.. The idea was to stream bluetooth audio.. i don't think this is fully supported yet either.. (aka there was a random driver/bugs..) 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/CAOCHtYgY5hqLY9pcXuUgHF9110gFvPRieqN59y6K%3DSqABvje6g%40mail.gmail.com.
Re: [beagleboard] Getting the RTC rv3028 to be used as /dev/rtc0
On Fri, Feb 5, 2021 at 4:39 AM Johan Ingvast wrote: > > Hi > > I have a RTC rv3028 on my system. It sits on i2c-2 at address 0x52. > I want it to update the system time with a correct time at each start of > system regardless contact to internet time or not. I have no need of the > alarm functions. > > RV3028 is really low power and claim to be accurate. > > I have checked it working using i2cset and i2cget. > > Now I want to have the system use it instead of the one not backed up battery. > > I found out that the most important registers of rv3028 are at the same place > as for the ds3231 that the kernel supports. This made me try > > $ echo ds3231 0x52 > /sys/class/i2c-dev/i2c-2/device/new_device > > and what I hoped happened. The /dev/rtc1 was created and responded with the > set time from > $ hwclock -r -f /dev/rtc1 > > But I still have some steps to take to make everything work. The system > should use the clock as /dev/rtc and use it at startup, correct the time and > so forth. > > I thought of using overlays, there is an overlay for ds3031 which codes for > another i2c address. > > Is it possible/enough to change bus and address of an existing ds3031 overlay > like > https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-RTC-DS3231.dts > to make it work for the rv3028? Correct, just update these 3 lines and it should just work.. https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-RTC-DS3231.dts#L81-L84 The rest is more informal that get's reported to userspace for your sanity to see if it loaded.. 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/CAOCHtYjuQi6iMSgydUh-R5bS0W5Z-cFTVFqC%2Bib%3DK1qhEkYGJQ%40mail.gmail.com.
Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13
On Thu, Feb 4, 2021 at 5:00 PM Hartley Sweeten wrote: > > Hello, > > I just did an 'apt update' and see that bb-cape-overlays has been updated. > > $ apt-mark showhold > bb-cape-overlays > > $ apt list --upgradable -a > Listing... Done > bb-cape-overlays/unknown 4.14.20201221.0-0~stretch+20201221 armhf [upgradable > from: 4.4.20190610.0-0rcnee0~stretch+20190610] > bb-cape-overlays/now 4.4.20190610.0-0rcnee0~stretch+20190610 armhf > [installed,upgradable to: 4.14.20201221.0-0~stretch+20201221] > > I still have that package on hold since it caused my boards not to boot. > > Any ideas what may be causing my boards not to boot when I upgrade that > package? Is the current package any better? I don't want to mess with it if > it breaks things again. As long as you are running 4.9.x based kernel, do NOT upgrade to the 4.14.x version of bb-cape-overlays as it only supports v4.14.x based kernels and later.. 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/CAOCHtYhqH8yBZON%3DDbncARj-Tw7hZS3Fy7sekVHNK-2aUq2Wtg%40mail.gmail.com.
Re: [beagleboard] Re: Image duplication
On Tue, Feb 2, 2021 at 7:53 PM Tom Stepleton wrote: > > I've never had trouble duplicating modified images --- it's how I distribute > the software for my own project. > > This said, I suspect (but haven't checked) that all PocketBeagles running my > images will have the same host key. It's not a big problem for me since my > application is a standalone appliance for retrocomputing (so you seldom ever > plug it into anything except the old computer and a power source). sudo touch /etc/ssh/ssh.regenerate and reboot, lots of things will get regenerated.. 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/CAOCHtYgrHFc2R6jUm%3D2vQGDWSZ%3D%2BzOs1Coe5qqmSNpTM%3DMg2Tw%40mail.gmail.com.
Re: [beagleboard] Image duplication
On Tue, Feb 2, 2021 at 6:15 PM Paul Beam wrote: > > Let's say I have tweaked an image for the PocketBeagle and want to duplicate > it for additional units. Is it valid to just duplicate my revised image, or > is there something unique that has to be done for each one? I seem to recall > somewhere in a boot script is something that runs only the first time, but I > currently can't find it and don't remember what it does. For the PocketBeagle, just dd the microSD to another microSD.. 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/CAOCHtYis9TTDd7DgtpJ18SJ0WyoKiJt7HRRwGnxgtcN9-7ERYQ%40mail.gmail.com.
Re: [beagleboard] Comms Cape
On Mon, Feb 1, 2021 at 5:24 PM Dwayne Zimmerman wrote: > > Thanks I have that. It doesn't detail the 4-20mA circut, unless I'm missing > something. I'm trying to understand where power comes from and at what > voltage. Each of those two connectors are connected to an adc pin. They both have a pull-down.. The ADC's can only take 1.8V, any more and they will fry.. 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/CAOCHtYi0SCvgoHPBED%2BZ6L%2B9BGfKiP2h2RFrkJtkUC%3Dkzbyr7Q%40mail.gmail.com.
Re: [beagleboard] Comms Cape
On Mon, Feb 1, 2021 at 5:06 PM Dwayne Zimmerman wrote: > > Looking for a wiring diagram for the 4-20ma on the beagle bone black coms cape https://github.com/beagleboard/capes/tree/master/beaglebone/Comms 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/CAOCHtYiCLjg1TNe157sLO-tu_-q_%2BtaRSHZYzKDKQZKayMoj4g%40mail.gmail.com.
Re: [beagleboard] Re: apt on BBB *very* slow, anyone else noticed?
> That seems much more reasonable, I wonder what's up with mine. > > Does running of an SD card rather than the EMMC slow things down a > lot? I have tried a bigger, newer SD card to see if it speeded > things up but it doesn't seem to have had much effect. > > Anyway at least it's not me imagining things! :-) Here's a recent change on this, pretty much we dropped our custom thing, and just copied the PI's configuration: https://github.com/RobertCNelson/omap-image-builder/commit/58d9d295cfc0e7b435cbe4d6cd71e534fbe3829b you can run sudo rm /etc/apt/apt.conf.d/02compress-indexes Disable PDiff's.. echo 'Acquire::PDiffs "0";' > /tmp/02-no-pdiffs sudo mv /tmp/02-no-pdiffs /etc/apt/apt.conf.d/02-no-pdiffs sudo chown root:root /etc/apt/apt.conf.d/02-no-pdiffs Then run: sudo apt update and you'll see about a 100MB's of free space removed.. But it's faster 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/CAOCHtYghrv5dQOeNt_TW6V7E3oExGXRM02oYV5xrNTKL2PMS8A%40mail.gmail.com.
Re: [beagleboard] Re: apt on BBB *very* slow, anyone else noticed?
On Mon, Feb 1, 2021 at 12:10 PM jonnymo wrote: > > How do you have your BB connected network wise. Also, what image are you > running? apt search is a cpu-cycle.. 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/CAOCHtYj%3D3%2BqaQcxVnb1QGreWFHBK6id4rUsN8oTNwspp1aRJhQ%40mail.gmail.com.
Re: [beagleboard] apt on BBB *very* slow, anyone else noticed?
On Mon, Feb 1, 2021 at 11:18 AM Chris Green wrote: > > I have recently done a clean install of Debian on a BBB and it feels > *very* slow, especially when running apt. Even 'apt search' just > crawls along at times. > > Has something changed to cause this or have I just got used to fast > hardware and forgotten what a BBB is like, or what? > > Here's a timing of a search:- > > chris@beaglebone$ time apt search vile > Sorting... Done > Full Text Search... Done > > [snip results] > > real4m4.103s > user3m55.675s > sys 0m7.152s > > Over four minutes for a simple search seems rather slow. > > I tried the same on an old Raspberry Pi :- > > chris@dns$ time apt search vile > Sorting... Done > Full Text Search... Done > > [snip results] > > real0m8.512s > user0m8.228s > sys 0m0.285s > > Just eight seconds, much more reasonable, so what's happened to the BBB? debian@bbb-pwr01-ser09:~$ time apt search vile Sorting... Done Full Text Search... Done bubblewrap/stable 0.3.1-4 armhf setuid wrapper for unprivileged chroot and namespace manipulation zulupolkit/stable 5.4.0-3 armhf handler the polkit privileges real 0m15.199s user 0m13.600s sys 0m1.135s model:[TI_AM335x_BeagleBone_Black] dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06] 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/CAOCHtYgif7WS9i1JdeTR6gajsUMTgccV4GmeLcN10M_8SprN6g%40mail.gmail.com.
