Re: [beagleboard] BBB no autoboot of uSD
So it ended up being ridiculously easy- thank you for all your work, Robert! I just switched the two if statements in the CONFIG_BOOTCOMMAND definition in am335x_evm.h (u-boot/include/configs) so that mmc dev 1 was attempted first. Now I have this u-boot.img on my eMMC and the original on the SD card. Now I can leave the SD card in there and only boot from it when I hold down S2 :) Best, Louis On Sunday, March 23, 2014 10:24:01 AM UTC-4, Louis Thiery wrote: > > Ah finally got my toolchain to work with these instructions: > http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot > > The u-boot.img I compiled out of there works just fine - so now let's see > what happens when I hack it :D > > On Saturday, March 22, 2014 12:46:51 PM UTC-4, Louis Thiery wrote: >> >> Jumping in a little late perhaps but my concern is slightly relevant to >> the discussion here. >> >> Nelson desribes the boot order: >> >> bootrom loads MLO from eMMC (if that fails it moves to microSD) >> MLO loads u-boot.img from eMMC >> u-boot.img first looks at microSD for uEnv.txt, reads that file in. >> >> I'd like to reverse that last step and make it to default to uEnv.txt >> from the eMMC. >> >> But I have no idea how to modify u-boot.img. What should I be reading? >> >> Or is there a u-boot.img that exists already that will allow me to boot >> off of the eMMC even if the flasher uSD is present (which I understand is >> the HW default)? >> >> Thanks, >> Louis >> >> On Friday, March 7, 2014 11:12:13 PM UTC-5, Loren Amelang wrote: >>> >>> My long but successful "learning experience" is reported in: >>> https://groups.google.com/forum/#!topic/beagleboard/zNtdwtPf2Q8 >>> >>> Definitely not simple, but possible... Without making any changes to >>> the eMMC installation! >>> >>> On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote: >>>> >>>> Robert, >>>> >>>> My BBB absolutely must default to booting from the uSD. I know I >>>> could short the boot switch, or move pull-up/down resistors, or create a >>>> hardware switch gated from reset, but I don't want to lose hardware >>>> compatibility with other BBB boards, or give up the option of manually >>>> booting from eMMC occasionally. The code you suggest here sounds perfect - >>>> but I'm not positive what to do with it. From the formatting of the text, >>>> I >>>> suspect it is intended to be compiled into a new u-boot.img and MLO image, >>>> but I'm not sure how to do that. >>>> >>>> Before I spend hours learning how, is there a chance I could just >>>> insert the basic ideas into my uEnv.txt as "mmcboot=mmc dev 0; if mmc >>>> rescan ; then ..."? It does look like uEnv.txt is read before the mmcboot >>>> command runs... >>>> >>> >>> >> -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB no autoboot of uSD
Ah finally got my toolchain to work with these instructions: http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot The u-boot.img I compiled out of there works just fine - so now let's see what happens when I hack it :D On Saturday, March 22, 2014 12:46:51 PM UTC-4, Louis Thiery wrote: > > Jumping in a little late perhaps but my concern is slightly relevant to > the discussion here. > > Nelson desribes the boot order: > > bootrom loads MLO from eMMC (if that fails it moves to microSD) > MLO loads u-boot.img from eMMC > u-boot.img first looks at microSD for uEnv.txt, reads that file in. > > I'd like to reverse that last step and make it to default to uEnv.txt from > the eMMC. > > But I have no idea how to modify u-boot.img. What should I be reading? > > Or is there a u-boot.img that exists already that will allow me to boot > off of the eMMC even if the flasher uSD is present (which I understand is > the HW default)? > > Thanks, > Louis > > On Friday, March 7, 2014 11:12:13 PM UTC-5, Loren Amelang wrote: >> >> My long but successful "learning experience" is reported in: >> https://groups.google.com/forum/#!topic/beagleboard/zNtdwtPf2Q8 >> >> Definitely not simple, but possible... Without making any changes to the >> eMMC installation! >> >> On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote: >>> >>> Robert, >>> >>> My BBB absolutely must default to booting from the uSD. I know I >>> could short the boot switch, or move pull-up/down resistors, or create a >>> hardware switch gated from reset, but I don't want to lose hardware >>> compatibility with other BBB boards, or give up the option of manually >>> booting from eMMC occasionally. The code you suggest here sounds perfect - >>> but I'm not positive what to do with it. From the formatting of the text, I >>> suspect it is intended to be compiled into a new u-boot.img and MLO image, >>> but I'm not sure how to do that. >>> >>> Before I spend hours learning how, is there a chance I could just insert >>> the basic ideas into my uEnv.txt as "mmcboot=mmc dev 0; if mmc rescan ; >>> then ..."? It does look like uEnv.txt is read before the mmcboot command >>> runs... >>> >> >> > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: How Flashing Now Works with Debian
Ah got everything working nicely :) Thanks for much for the help, Nelson. I especially like the script located at: /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh On Friday, March 21, 2014 4:59:24 PM UTC-4, Louis Thiery wrote: > > Cool - I don't think I've ever played with such structured scripts before! > > I've gotten up to the board specific script and I get the following: > Valid EEPROM header found > sed: can't read /etc/default/udhcpd: No such file or directory > cat: /etc/udhcpd.conf: No such file or directory > /opt/scripts/boot/am335x_evm.sh: line 85: /etc/udhcpd.conf: Read-only file > system > /opt/scripts/boot/am335x_evm.sh: line 86: /etc/udhcpd.conf: Read-only file > system > /opt/scripts/boot/am335x_evm.sh: line 87: /etc/udhcpd.conf: Read-only file > system > /opt/scripts/boot/am335x_evm.sh: line 88: /etc/udhcpd.conf: Read-only file > system > /opt/scripts/boot/am335x_evm.sh: line 89: /etc/udhcpd.conf: Read-only file > system > /opt/scripts/boot/am335x_evm.sh: line 91: /etc/init.d/udhcpd: No such file > or directory > SIOCSIFADDR: No such device > usb0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > /opt/scripts/boot/am335x_evm.sh: line 94: /usr/sbin/udhcpd: No such file > or directory > Device "usb0" does not exist. > Device "wlan0" does not exist. > sed: couldn't open temporary file /etc/sedXOJqCd: Read-only file system > /opt/scripts/boot/am335x_evm.sh: line 103: /etc/issue: Read-only file > system > > It seems that the main issue is that the partition that I'm running is > read-only... I don't know when I set it as such and chmod'ing the whole > thing didn't seem to resolve. > > I guess I'll built my distro over again and try to find out at which point > I made it "read-only" > > On Friday, March 21, 2014 3:26:11 PM UTC-4, RobertCNelson wrote: >> >> On Fri, Mar 21, 2014 at 2:22 PM, Louis Thiery >> wrote: >> > Just to see if it would "just work", I tried to run the script from my >> > distribution and the scrip is unhappy: >> > >> > /bin/bash /opt/scripts/beaglebone-black-eMMC-flasher.sh >> > Error: script halting, system unrecognized... >> >> The "script" assumes a few things, so i have a couple quick system >> checks, that make it stop if it doesn't recognize the system.. >> >> Regards, >> >> -- >> Robert Nelson >> http://www.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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB no autoboot of uSD
Jumping in a little late perhaps but my concern is slightly relevant to the discussion here. Nelson desribes the boot order: bootrom loads MLO from eMMC (if that fails it moves to microSD) MLO loads u-boot.img from eMMC u-boot.img first looks at microSD for uEnv.txt, reads that file in. I'd like to reverse that last step and make it to default to uEnv.txt from the eMMC. But I have no idea how to modify u-boot.img. What should I be reading? Or is there a u-boot.img that exists already that will allow me to boot off of the eMMC even if the flasher uSD is present (which I understand is the HW default)? Thanks, Louis On Friday, March 7, 2014 11:12:13 PM UTC-5, Loren Amelang wrote: > > My long but successful "learning experience" is reported in: > https://groups.google.com/forum/#!topic/beagleboard/zNtdwtPf2Q8 > > Definitely not simple, but possible... Without making any changes to the > eMMC installation! > > On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote: >> >> Robert, >> >> My BBB absolutely must default to booting from the uSD. I know I >> could short the boot switch, or move pull-up/down resistors, or create a >> hardware switch gated from reset, but I don't want to lose hardware >> compatibility with other BBB boards, or give up the option of manually >> booting from eMMC occasionally. The code you suggest here sounds perfect - >> but I'm not positive what to do with it. From the formatting of the text, I >> suspect it is intended to be compiled into a new u-boot.img and MLO image, >> but I'm not sure how to do that. >> >> Before I spend hours learning how, is there a chance I could just insert >> the basic ideas into my uEnv.txt as "mmcboot=mmc dev 0; if mmc rescan ; >> then ..."? It does look like uEnv.txt is read before the mmcboot command >> runs... >> > > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: How Flashing Now Works with Debian
Cool - I don't think I've ever played with such structured scripts before! I've gotten up to the board specific script and I get the following: Valid EEPROM header found sed: can't read /etc/default/udhcpd: No such file or directory cat: /etc/udhcpd.conf: No such file or directory /opt/scripts/boot/am335x_evm.sh: line 85: /etc/udhcpd.conf: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 86: /etc/udhcpd.conf: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 87: /etc/udhcpd.conf: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 88: /etc/udhcpd.conf: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 89: /etc/udhcpd.conf: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 91: /etc/init.d/udhcpd: No such file or directory SIOCSIFADDR: No such device usb0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device /opt/scripts/boot/am335x_evm.sh: line 94: /usr/sbin/udhcpd: No such file or directory Device "usb0" does not exist. Device "wlan0" does not exist. sed: couldn't open temporary file /etc/sedXOJqCd: Read-only file system /opt/scripts/boot/am335x_evm.sh: line 103: /etc/issue: Read-only file system It seems that the main issue is that the partition that I'm running is read-only... I don't know when I set it as such and chmod'ing the whole thing didn't seem to resolve. I guess I'll built my distro over again and try to find out at which point I made it "read-only" On Friday, March 21, 2014 3:26:11 PM UTC-4, RobertCNelson wrote: > > On Fri, Mar 21, 2014 at 2:22 PM, Louis Thiery > > > wrote: > > Just to see if it would "just work", I tried to run the script from my > > distribution and the scrip is unhappy: > > > > /bin/bash /opt/scripts/beaglebone-black-eMMC-flasher.sh > > Error: script halting, system unrecognized... > > The "script" assumes a few things, so i have a couple quick system > checks, that make it stop if it doesn't recognize the system.. > > Regards, > > -- > Robert Nelson > http://www.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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: How Flashing Now Works with Debian
Oops - just saw your reply. Will study what you describe On Friday, March 21, 2014 3:22:15 PM UTC-4, Louis Thiery wrote: > > Just to see if it would "just work", I tried to run the script from my > distribution and the scrip is unhappy: > > /bin/bash /opt/scripts/beaglebone-black-eMMC-flasher.sh > Error: script halting, system unrecognized... > > > > On Friday, March 21, 2014 1:51:55 PM UTC-4, Louis Thiery wrote: >> >> Hello, >> >> I'm trying to leverage the flashing process included in the new Debian >> images to move my own distribution over but I'm confused on the current >> mechanics. >> >> I did find this page: http://elinux.org/Beagleboard:Updating_The_Software >> >> but perhaps that explains how flashing used to work with Angstrom? I >> wasn't able to see the same architecture happening over on the new Debian >> images which works in 15 minutes instead of 45 minutes. >> >> I did find */opt/scripts/tools/beaglebone-black-eMMC-flasher.sh *but I'm >> not particularly sure of the mechanics. >> >> It seems to me that when the boot button is pressed, the BBB mounts and >> boots from the eMMC-flasher partition. Somehow this script is executed (I >> couldn't find the relevant systemd process) and it copies over everything >> on that same partition over to the eMMC and then powers off. >> >> Next time, I boot from the eMMC, how does the script knows to not >> execute, seeing as it can't really copy the eMMC to the eMMC... How does >> all this work? >> >> Thanks, >> Louis >> > -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: How Flashing Now Works with Debian
Just to see if it would "just work", I tried to run the script from my distribution and the scrip is unhappy: /bin/bash /opt/scripts/beaglebone-black-eMMC-flasher.sh Error: script halting, system unrecognized... On Friday, March 21, 2014 1:51:55 PM UTC-4, Louis Thiery wrote: > > Hello, > > I'm trying to leverage the flashing process included in the new Debian > images to move my own distribution over but I'm confused on the current > mechanics. > > I did find this page: http://elinux.org/Beagleboard:Updating_The_Software > > but perhaps that explains how flashing used to work with Angstrom? I > wasn't able to see the same architecture happening over on the new Debian > images which works in 15 minutes instead of 45 minutes. > > I did find */opt/scripts/tools/beaglebone-black-eMMC-flasher.sh *but I'm > not particularly sure of the mechanics. > > It seems to me that when the boot button is pressed, the BBB mounts and > boots from the eMMC-flasher partition. Somehow this script is executed (I > couldn't find the relevant systemd process) and it copies over everything > on that same partition over to the eMMC and then powers off. > > Next time, I boot from the eMMC, how does the script knows to not execute, > seeing as it can't really copy the eMMC to the eMMC... How does all this > work? > > Thanks, > Louis > -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How Flashing Now Works with Debian
Hello, I'm trying to leverage the flashing process included in the new Debian images to move my own distribution over but I'm confused on the current mechanics. I did find this page: http://elinux.org/Beagleboard:Updating_The_Software but perhaps that explains how flashing used to work with Angstrom? I wasn't able to see the same architecture happening over on the new Debian images which works in 15 minutes instead of 45 minutes. I did find */opt/scripts/tools/beaglebone-black-eMMC-flasher.sh *but I'm not particularly sure of the mechanics. It seems to me that when the boot button is pressed, the BBB mounts and boots from the eMMC-flasher partition. Somehow this script is executed (I couldn't find the relevant systemd process) and it copies over everything on that same partition over to the eMMC and then powers off. Next time, I boot from the eMMC, how does the script knows to not execute, seeing as it can't really copy the eMMC to the eMMC... How does all this work? Thanks, Louis -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Trying to enable UART
same deal, I'm afraid. > export SLOTS=/sys/devices/bone_capemgr.9/slots > echo BB-uART4 > $SLOTS -bash: echo: write error: No such file or directory On Sunday, March 16, 2014 3:24:38 PM UTC-4, Mike Bell wrote: > > On 03/16/2014 12:51 PM, Louis Thiery wrote: > > > > > > > echo BB-uART4-00A0 > $SLOTS > > -bash: echo: write error: No such file or directory > > > > $SLOTS is an environmental variable pointing to > > /sys/devices/bone_capemgr.9/slots > > > > I'm not sure how I can cat $SLOTS, see what I expect, but then not be > > able to output to it?! > > > Your $SLOTS variable is fine. > > Just lose the -00A0 i.e. > > echo BB-uART4 > $SLOTS > > Mike > -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Trying to enable UART
I'm a little confused... FYI I'm running ArchLinux on BBB, but I get this error: > cat $SLOTS 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI > echo BB-uART4-00A0 > $SLOTS -bash: echo: write error: No such file or directory $SLOTS is an environmental variable pointing to /sys/devices/bone_capemgr.9/slots I'm not sure how I can cat $SLOTS, see what I expect, but then not be able to output to it?! I'm sure it's something silly - I just can't figure it out :S -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BBB and SPI (again)
I often use this image as a pin reference: http://cholla.mmto.org/computers/beagle/BBBlack%20GPIO%20Map.png There's also the datasheet but that will take a while... On Monday, October 21, 2013 10:34:59 AM UTC-4, Alex wrote: > > Hi Guys, > > i hope someone can help me. > > After playing around with RaPi it is time now for BeagleBoard. > > So i bought me a BBB. > > I was a bit confused that there is only this google group and no forum in > a better "forum-style" what would be much better than this here. > Ok, so what... > > What i would like to do is: Get my WS2801 LED´s running on the BBB via > spidev > > That was no problem on my RaPi. > But here at the BBB it is complete different. I read a lot about > activating SPIDEV and it seems to be OK. i can activate SPI0 so i have > /dev/spidev1.0 and i can also activate SPI1 when i disable HDMI at the > optargs so i get /dev/spidev2.0 > > Next step are the wires. i need Clock and Data(MOSI) for the WS2801 LED´s. > Am i right that at SPI0 these are 18 and 22 at P9 ? > > i tried a lot of combinations and every time i connect the WS2801 and > activate the SPI0 the first LED is active and flashes orange. > > I am not a pro in programming but i hope i can find some help here. > > At the moment i use Debian Wheezy but i also tried the angstrom but i > prefere to use debian but if i have to, i will change back to angstrom. > > So, it would be great if someone can give me a help to geht these LEDs > wired and running. > > Regards > Alex > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
