[beagleboard] Re: Advice needed on building a device tree overlay
Robert, here is the output of version.sh. $ sudo ./version.sh git:/opt/scripts/:[7f60eba275c0b3d0c1c826d410de25961cc4ed94] eeprom:[A335BNLT000C1633BBBG0596] model:[TI_AM335x_BeagleBone_Black] dogtag:[rcn-ee.net console Ubuntu Image 2018-08-10] bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.03-2-gac9cce7c6a]:[location: dd MBR] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2016.03-1-gd12d09f]:[location: dd MBR] kernel:[4.14.62-ti-r69] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-UART2-00A0.dtbo] uboot_overlay_options:[uboot_overlay_addr1=/lib/firmware/BB-I2C2-RTC-DS1307.dtbo] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-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.4.20180914.0-0rcnee0~bionic+20180914] pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~bionic+20180517] pkg:[kmod]:[24-1ubuntu3rcnee0~bionic+20180515] WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED] groups:[ubuntu : ubuntu adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep admin spi tisdk weston-launch xenomai cloud9ide] cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] dmesg | grep pinctrl-single [1.128558] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 dmesg | grep gpio-of-helper [1.129754] gpio-of-helper ocp:cape-universal: ready END > > Actually we have an alias swap going on... The am335x's un-useful rtc > > becomes /dev/rtc1 and the DS1307 becomes /dev/rtc0, thus all the > > standard clock programs just work with the external rtc.. > I'm glad the DS1307 becomes /etc/rtc0. That makes things easier. > > And the ds1307 module is usually built in, so you won't see the module > > thru lsmod... > This is good to know. I was looking at the output of lsmod and wondering why I didn't see module rtc-ds1307.ko. I know that the slots file (/sys/devices/platform/bone_capemgr/slots) is now disabled in my kernal (4.14.62-ti-r69). But I think the bone_capemgr is still enabled. dmesg shows this: bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,000C,1633BBBG0596' bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4 bone_capemgr bone_capemgr: slot #0: No cape found bone_capemgr bone_capemgr: slot #1: No cape found bone_capemgr bone_capemgr: slot #2: No cape found bone_capemgr bone_capemgr: slot #3: No cape found bone_capemgr bone_capemgr: initialized OK. Should I see BB-UART2-00A0.dtbo in slot #0 and BB-I2C2-RTC-DS1307.dtbo in slot #1? Or is there another way to tell if the overlays have been loaded? Thanks for your help, Tim -- 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/b1cc5275-f54f-4564-9b7d-e7681dd50a26%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Advice needed on building a device tree overlay
> > > I forgot to say I have Robert Nelsons Ubuntu 18.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic -- 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/92333d75-e6b2-4e4f-9368-069df6d5b6fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Advice needed on building a device tree overlay
I did the following: - I fetched https://github.com/beagleboard/bb.org-overlays - copied the file BB-I2C2-RTC-DS1338.dts to BB-I2C2-RTC-DS1307.dts - edited BB-I2C2-RTC-DS1307.dts to refer to my DS1307 chip instead of DS1338 - make src/arm/BB-I2C2-RTC-DS1307.dtbo - sudo cp ./src/arm/BB-I2C2-RTC-DS1307.dtbo /lib/firmware/ I added the following lines to /boot/uEnv.txt: uboot_overlay_addr0=/lib/firmware/BB-UART2-00A0.dtbo uboot_overlay_addr1=/lib/firmware/BB-I2C2-RTC-DS1307.dtbo I rebooted. After rebooting, dmesg shows this: bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,000C,1633BBBG0596' bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4 bone_capemgr bone_capemgr: slot #0: No cape found bone_capemgr bone_capemgr: slot #1: No cape found bone_capemgr bone_capemgr: slot #2: No cape found bone_capemgr bone_capemgr: slot #3: No cape found bone_capemgr bone_capemgr: initialized OK. I expected to see BB-UART2-00A0.dtbo in slot #1 and BB-I2C2-RTC-DS1307.dtbo in slot #2. The overlays are not loaded. What am I doing wrong? I also expect that loading the overlay BB-I2C2-RTC-DS1307.dtbo will create /dev/rtc1, and also load the module rtc-ds1286.ko. Am I correct in thinking this? Thanks for your help, Tim -- 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/00c6beb3-451b-4781-9e19-39ffe35a2369%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Advice needed on building a device tree overlay
How do I install a single overlay? I'm writing and building a device tree overlay for a RTC chip (a DS1307) on a cape board that we designed. I want to communicate with the chip over the I2C bus no. 2 on a beaglebone black. I know how to build the overlay using dtc, and I know I must copy the .dtbo file to /lib/firmware. My question is, do I have to run update-initramfs as well, or is it good enough to copy the .dtbo file to /lib/firmware? Anything else I need to do to install a single .dtbo? Another question: I see there is an overlay (BB-I2C2-RTC-DS1338.dts) available on https://github.com/RobertCNelson/bb.org-overlays. Maybe this will work for me with my DS1307 chip? Or I could install all the overlays with sudo apt update; sudo apt install bb-cape-overlays. Is it safe to install all the currently available overlays from Robert Nelson's site on my system? I have an older version of Ubuntu (16.04.3 LTS from Robert Nelson). Thanks, Tim -- 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/ee0c9b5b-4ca5-4d5d-a26f-b12905e0a624%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: How to boot from microSD card image, not from the onboard flash?
Greg, I downloaded this Ubuntu image (not a Debian image) and installed it on my microSD: > > https://rcn-ee.com/rootfs/2017-07-14/microsd/bone-ubuntu-16.04.2-console-armhf-2017-07-14-2gb.img.xz > Are you saying that if I uncomment that line in /boot/uEnv.txt and reboot, the image I just copied to the microSD will be copied to eMMC? I assume that after flashing the eMMC, I must comment that line again to avoid flashing the eMMC on every boot. Is it necessary to have the same image in both eMMC and microSD to support automatic booting from microSD? I assume I must flash the 2GB image to eMMC, before I resize the microSD partition to 8GB (the 8GB image won't fit in eMMC). My goal is to boot from an 8GB microSD everytime, not eMMC. I really don't care what's in eMMC, I want to reliably boot from microSD. To confuse matters further, I noticed that there is also a "flasher" image available: > > https://rcn-ee.com/rootfs/2017-07-14/flasher/BBB-eMMC-flasher-ubuntu-16.04.2-console-armhf-2017-07-14-2gb.img.xz > What's the difference between the "microSD" and "flasher" images? This is confusing. Thanks, Tim -- 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/7190ecb7-54c8-436c-8e6d-537475d9b03d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to boot from microSD card image, not from the onboard flash?
I have a new BBB (Beaglebone Black, rev C). I just installed Robert Nelsons's latest Ubuntu image on a microSD card (https://rcn-ee.com/rootfs/2017-07-14/microsd/bone-ubuntu-16.04.2-console-armhf-2017-07-14-2gb.img.xz). The onboard eMMC has the default Debian that came with the BBB. I don't really care what's installed in the onboard flash. I want to boot from the microSD card image, not from the onboard flash. What's the best way to make my Beaglebone boot from the microSD card WITHOUT having to push the BBB's boot button during power-on? Thanks, Tim M -- 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/692ca753-7bc0-4b66-b825-73433f3bb96b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Need Ubuntu version that supports capemgr
I want to install a version of Ubuntu on a Beaglebone Black rev C that supports the capemgr. I will be using an XBee cape and want to enable UART2 by adding "cape_enable=capemgr.enable_partno=BB-UART2" to /boot/uEnv.txt. I will also need to enable an i2c port to interface to a real time clock chip, also by using capemgr. I prefer to use an Ubuntu image that I can simply write to a microSD card. I was thinking of using Robert Nelson's image https://rcn-ee.com/rootfs/2017-01-23/microsd/bone-ubuntu-16.04.1-console-armhf-2017-01-23-2gb.img.xz Does anyone know if this image supports the capemgr? I'm not opposed to a Debian image, if I can write it to a microSD card and it supports capemgr. Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f4f16dd5-3752-47fe-9fe3-420ed409e452%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
Robert, I installed Ubuntu (not Debian), by following your instructions for copying the raw microSD image to the microSD card: http://elinux.org/BeagleBoardUbuntu#BeagleBone.2FBeagleBone_Black Then I inserted the card in the BBB, held down the boot button while powering up, and it booted from the card. If I reboot, it boots from the microSD card, which is what I want. If I remove the card and power up, it boots from the eMMC. Do I need to flash anything to the eMMC? The eMMC still has the default Debian. Since the BBB boots from the card as desired, maybe I don't need to do anything to the eMMC. I have one question. I will be using a XBee cape board that needs UART2 to be enabled. I will need to add a line like this to uEnv.txt: optargs=capemgr.enable_partno=BB-UART2 I think I should add this line /boot/uboot/uEnv.txt in the eMMC, am I right? I ask this because the microSD card has two copies, /uEnv.txt and /boot/uEnv.txt. The contents of these two files and the file in eMMC are different. Thanks, Tim -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
Robert,
Holding down the boot button doesn't work, I get the Bad Linux ARM zImage
magic error mentioned above.
When you say it has a later version of u-boot, do you mean the eMMC has a
later version of uboot than my microSD card?
How would I fix my uEnv.txt? Here is my uEnv.txt script from the microSD
card (which is different than eEnv.txt in the eMMC):
mmcpart=2
mmcrootfstype=ext4 rootwait
optargs=fixrtc capemgr.enable_partno=BB-UART2
uenvcmd=i2c mw 0x24 1 0x3e; setenv mmcroot /dev/mmcblk${mmcdev}p${mmcpart}
ro
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${bootdir}/dtbs/${fdtfile}
loadimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${bootdir}/${bootfile}
Remember, my microSD card has Ubuntu 12.04.5 LTS
(ubuntu-precise-12.04.3-armhf-3.8.13-bone30.img.xz downloaded from
http://www.armhf.com/) and my eMMC has the default Debian that came
installed on the BBB.
Here is what I've done
1. Copy Ubuntu image to the microSD card (as per
http://www.armhf.com/index.php/getting-started-with-ubuntu-img-file/)
2. Plug card into BBB and boot from card by holding down the boot button
3. Copy Ubuntu image to the onboard eMMC
4. From that point forward, BBB will boot from microSD card without having
to hold down the boot button.
I have six BBB's. I followed these steps for all six, and it worked with
the first five BBB's. It's only the sixth BBB that is giving me this
trouble. The sixth refuses to boot from the microSD.
Thanks for your help Robert, I'm just not sure how to get this sixth
beaglebone working.
Tim
--
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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
Robert, I haven't actually written the Ubuntu image to eMMC yet (I have on the first five BBB's but not on the sixth, I can't get past step 1 on the sixth). This is my goal. 1. Get Ubuntu installed on a microSD card. 2. Configure the BBB to boot from the microSD WITHOUT pressing the boot button every time it boots. I really don't care what version of Linux is in the eMMC, I just want the BBB to automatically boot from the microSD card. The BBB will be accessed and rebooted remotely, without a human present to push the button. I will look at the links you provided. Will the instructions on the links you provided help me reach my goal? Thanks for your help, Tim -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
. William, thanks for your help. I will have to buy a FTDI cable before I can give this a try. But I have a question. My BBB doesn't boot from a microSD, all LEDs come on immediately and stay on. How can I connect to it in this state? If I have a serial console connection to the BBB using the FTDI cable, will I have to log in with a user name and password? Or will it behave as if I had a monitor attached, and boot messages will simply appear on screen? I'm trying to determine if getting an FTDI cable will help debug this failure to boot problem. Thanks for your help everyone. -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
Robert, could I connect a keyboard and monitor and see the boot messages on the monitor, the same boot messages that would appear on the serial console? I'm asking because I could connect a monitor today, but I'd have to order a FTDI cable, which would take a few days to arrive. Thanks, Tim -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
I've held down the button you're suggesting for nearly 2mins and no change from booting from uSD. Once I eject the uSD and reboot the BBB i'm able to boot into to the eMMC, which is running the flashed version of ubuntu. I'm simply attempting to run the ubuntu desktop now(from uSD), instead of the console version (on eMMC). I'm having the same problem as A M Kent. I have a BBB rev C. I've installed Ubuntu 12.04.2 on a microSD card, and the card is inserted in my BBB. When I turn on the power while holding down the boot switch, all 4 LEDs come on and remain lit. The BBB does not boot. I held down the boot switch a long time (about 60 seconds). Once I eject the microSD and reboot the BBB I'm able to boot into to the eMMC, which still contains the Debian that came installed on the BBB. I have 5 other Beaglebone Blacks, all rev C, and they all boot just fine from a microSD card with Ubuntu 12.04.2. In fact, I took the microSD card from one of these BBBs and inserted it in my new BBB, and it doesn't boot. This seems to indicate that my new BBB is defective. Do you guys agree? Tim M -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
Robert, Unfortunately I don't have a ftdi usb-serial cable. But if I get one, can you refer me to instructions on how to use it? Thanks, Tim -- 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: Beaglebone Black won't boot from Micro SD, all LEDs remain lit
I meant that I've never used the debug port and an FTDI cable on the BBB. I assume I would connect to the BBB using a serial terminal program (in my case I would be connecting from Windows). When Robert said I could prove it easily by plugging in a ftdi usb-serial cable into the debug port, I assume he means that I can get an idea of what's happening by watching the messages on the serial terminal. Am I right? -- 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.
