Re: [beagleboard] Re: very quick questions: startup of lxde, exports, usb babble, and shutdown
towards item [1] I think that something like systemctl disable graphical.target will stop it from booting into an x environment (for systemd inits). I don't know if systemctl enable graphical.target will start it up again or just re-enable it for the next boot. Maybe check a systemd guide for Fedora and try some of their commands (Systemd guidance is pretty sparse in the Debian world.) Cheers. -- 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: very quick questions: startup of lxde, exports, usb babble, and shutdown
try: # systemctl isolate multi-user.target (or) # systemctl isolate runlevel3.target to turn of X without rebooting and to turn it back on try: # systemctl isolate graphical.target (or) #systemctl isolate runlevel5.target On Sun, Jan 11, 2015 at 9:56 PM, Jason Lange j.b.la...@gmail.com wrote: towards item [1] I think that something like systemctl disable graphical.target will stop it from booting into an x environment (for systemd inits). I don't know if systemctl enable graphical.target will start it up again or just re-enable it for the next boot. Maybe check a systemd guide for Fedora and try some of their commands (Systemd guidance is pretty sparse in the Debian world.) Cheers. -- 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] Newbie question about I/O on the beaglebone black...
If you don't want to get into PRU programming ordinary sequential IO and a latched buffer might work for you. On Thu, Sep 25, 2014 at 11:36 PM, John Tonkin john.ton...@gmail.com wrote: hi there your project is a little mysterious, so it is hard to be specific but here are some thoughts based on my own recent research into using beaglebones to drive LEDstrips and a custom LCD array. from https://github.com/osresearch/LEDscape the beaglebone SOC has two PRUs (programmable realtime unit) which are designed for this sort of purpose. the TI AM335x ARM Cortex-A8 in the BeagleBone Black has two programmable microcontrollers built into the CPU that can handle realtime tasks and also access the ARM's memory. This allows things that might have been delegated to external devices to be handled without any additional hardware, and without the overhead of clocking data out the USB port. (I am actually using a fork of this library https://github.com/Yona-Appletree/LEDscape for driving LED strips, and am planning to modify this code for my other project) PRUs run at 200MHz and have very efficient access to some (more than the 16 bits that you require) of the GPIO pins (these need to be pin-muxed correctly - that is another can of worms / kettle of fish). you read / write to pins by reading / writing to specific PRU registers. so you can read/write 8 (or more) bits simultaneously. it's much more efficient than the more traditional Linux sysfs approach. there is a FAQ about using the PRUs stickied at the top of this group and lots more info on The internet's. Trammell Hudson, who developed the original LEDscape code, seems to have done quite a bit of interfacing beaglebones to old computing hardware. http://trmm.net/Category:Retrocomputing eg http://trmm.net/Mac-SE_video another example http://blinkenbone.com/projects/blinkenbone I've found a logic analyser (eg https://www.saleae.com) to be very useful when doing this sort of stuff. john -- 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. -- 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] Switching to Jessie from Wheezy.
@Robert -- How do I switch to Jessie? (I notice gcc-4.9 is a happening thing for your latest jessie images and suspect that jessie is further along in it's support for systemd, but your your latest console images are wheezy only.) apt-get dist-upgrade didn't work. I thought about trying a search and replace wheezy/jessie in apt-sources but there must be a better way. Thanks in advance / IOU beer. Cheers. -- 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] Switching to Jessie from Wheezy.
That was rude of me; the answer was pretty much low hanging fruit, and I
didn't have the sense to look.
However I did have one glitch and I don't know that it's not important...
This is what I did:
# apt-get update
# apt-get upgrade
# cp /etc/apt/sources.list{,.bak}
# sed -i -e 's/wheezy/jessie/g' /etc/apt/sources.list
# apt-get update
At this point it became apparent that this line from my new
/etc/apt/sources file was not working:
deb [arch=armhf] http://debian.beagleboard.org/packages jessie-bbb main
I continued anyway with:
# apt-get update
# reboot
Things seem to have worked out.
But if someone sees a problem with that one repo not translating over
to jessie please let me know
(otherwise I'll just comment it out to get rid of the warnings)
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Switching to Jessie from Wheezy.
# apt-get update # reboot ..that's meant to be: apt-get dist-update -- 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] Switching to Jessie from Wheezy.
# apt-get update # reboot ..that's meant to be: apt-get dist-update damn.. that's apt-get dist-upgrade -- 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: Kernel 3.13 and above: How to enable dcan_1 and GPIOs
Hi Marco, I just enabled can0 using kernel 3.14.25-ti-r37 and the dtb-rebuilder (it's showing up with ifconfig -a, I haven't tested it further). It was pretty painless. Is there a strong reason not to use this kernel? If not a simple apt-get install linux-image-3.14.25-ti-r37 could be all you really need. Good luck. ps. I did have to apply this patch even though I did a git pull before modifying the .dts (@Robert is this right?) - pinctrl-single,pins = 0x180 * 0x32*; }; /* Mode 2, Pull-Up, RxActive */ //This line changes to + pinctrl-single,pins = 0x180 *0x12*; }; /* Mode 2, Pull-Up, RxActive */ //this one -- 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: Kernel 3.13 and above: How to enable dcan_1 and GPIOs
Hi Marco, About the patch: I think I made a mistake and changed a *similar* line by hand. I wasn't checking too carefully because I'm not actually using can0 -- I just wanted to tell you that it was going to work so you could stop wasting your time. I reverted the repo to be sure, and now I can't find the line. Probably a git pull is all you need to ensure you have the latest and greatest code. Cheers. -- 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] a question about asking questions
On Mon, Nov 24, 2014 at 11:05 PM, janszymanski12...@gmail.com wrote: Hi, I have still unresolved issue (no answer here for how to make pwm_P8_13 low on boot? ) and therefore trying to figure out if my question is: - too easy - too difficult - not interesting enough - other? As I see there is generally a number of unanswered questions, would it be possible for the moderator to give an indication in a simple style, something like: too easy, google it yourself or whatever, to avoid frustration. Jan Is there a moderator? I don't know. But for myself, your question is both too difficult (I don't know the answer) and not interesting enough (It isn't a problem that I need to solve for myself). Everybody here is going to have a different response, so having a moderator decide is probably a bit ham fisted. I can imagine an external hardware solution because I do circuits, but it'd be more elegant if someone helped you find a proper on-board software solution. If you find a solution on your own please post it. If you get desperate enough to start soldering email me and I'll try to help. Cheers. -- 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: Kernel 3.13 and above: How to enable dcan_1 and GPIOs
this: https://groups.google.com/forum/#!topic/beagleboard/WuCvPyi9bqk suggests that you might be more interested in this: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb On Tue, Nov 25, 2014 at 12:55 AM, Marco Steger marco.st1...@gmail.com wrote: Hi again! I spent some more hours on how to enable the d_can interfaces on my BBB. I found Robert Nelsons Really Simple Cape Manager (RSCM) here [1]. This looks very promising at first. There is a folder for 3.13-bone and the README says that 3.13-rc6-bone2 should be installed. I'm currently working on 3.16.1-bone4. As far as I understand the idea behind Robert’s RSCM I would need the original .dts file of my BBB. Than add the needed lines to enable d_can1 (to enable d_can0 I would have to disable I2C2. Am I right?). The build a dtb file using dtc (patched by Robert … he is present everywhere on the BBB I think! J) . Finally I can move this file to /boot/dtbs/3.16.1-bone4/ on my BBB (replace the existing dtb file(s). But where can I find the dts file of my BBB? I wasn’t able to locate it on my board. Can I use the dts file from 3.13? Can I (permanently) damage my BBB when playing around here? Would be great if someone can help me!!! [1] https://github.com/RobertCNelson/rscm -- 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. -- 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: Kernel 3.13 and above: How to enable dcan_1 and GPIOs
...the instructions are pretty lousy. If it's incomprehensible say so. I'll help. On Tue, Nov 25, 2014 at 1:39 AM, Jason Lange j.b.la...@gmail.com wrote: this: https://groups.google.com/forum/#!topic/beagleboard/WuCvPyi9bqk suggests that you might be more interested in this: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb On Tue, Nov 25, 2014 at 12:55 AM, Marco Steger marco.st1...@gmail.com wrote: Hi again! I spent some more hours on how to enable the d_can interfaces on my BBB. I found Robert Nelsons Really Simple Cape Manager (RSCM) here [1]. This looks very promising at first. There is a folder for 3.13-bone and the README says that 3.13-rc6-bone2 should be installed. I'm currently working on 3.16.1-bone4. As far as I understand the idea behind Robert’s RSCM I would need the original .dts file of my BBB. Than add the needed lines to enable d_can1 (to enable d_can0 I would have to disable I2C2. Am I right?). The build a dtb file using dtc (patched by Robert … he is present everywhere on the BBB I think! J) . Finally I can move this file to /boot/dtbs/3.16.1-bone4/ on my BBB (replace the existing dtb file(s). But where can I find the dts file of my BBB? I wasn’t able to locate it on my board. Can I use the dts file from 3.13? Can I (permanently) damage my BBB when playing around here? Would be great if someone can help me!!! [1] https://github.com/RobertCNelson/rscm -- 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. -- 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: Serial Wiring For External Device Over UART1
It looks good to me, as long as you are drawing less then 250ma. On Tue, Nov 25, 2014 at 12:41 AM, pietersydneythe...@gmail.com wrote: I've been trying to attach a serial device to the beaglebone black and communicating with it over UART 1 (p9_24 and p9_26) with no success. In part because I am new to linux and have no idea how to ping/check connected devices over terminal and NO prior electronic knowledge to insure the device is properly wired up to the beaglebone black. I've attached a wiring diagram below. Can someone please confirm: 1. That I've wired it correctly by looking at the diagram 2. That the supplied voltage from the BBB is sufficient to power the attached device (3.3V TTL) Mapping explained (see device diagram): Pin 1 VCC (P) to 3.3Vdc on the BBB (p9_03) Pin 2 GND (G) to GND on the BBB (p9_01) PIN 3 TXD (O) to UART1 RX on the BBB (p9_26) PIN 4 RXD (I) to UART1 TX on the BBB (p9_24) https://lh3.googleusercontent.com/-ydiICNM4U4I/VHQ-aW5xjzI/Anw/wJnRP_pSdso/s1600/BBBSerialDiagram.png Regards Pieter -- 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. -- 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 to make pwm_P8_13 low on boot?
From hardware you could use a 74HC04 to invert the signal. No need for an
additional enable line.
Cheers.
On Tue, Nov 25, 2014 at 1:27 PM, ja...@bigpond.net.au ja...@bigpond.net.au
wrote:
Thanks Peter,
I have exercised that option already before posting and somehow it didn't
work.
Changing the parameters (and recompiling) didn't change the default
values, so my conclusion is that they might be
somehow hard-coded in a kernel driver.
Jan
--
On 26/11/2014 12:34 AM Peter Gregory wrote:
I don't know if this will help, but have you tried changing the polarity
of the PWM pin in the device tree overlay?
bs_pwm_test_P8_13 {
compatible = pwm_test;
pwms = ehrpwm2 1 50 0;
pwm-names = PWM_P8_13;
pinctrl-names = default;
pinctrl-0 = bs_pwm_P8_13_0xc;
enabled = 1;
duty = 0;
status = okay;
};
The last numeric parameter of pwms ehrpwm2 1 50 0 swaps the
polarity of the PWM output.
With the default duty cycle of 0, the pin will be low on power-up.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the
Google Groups BeagleBoard group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/bqsOg6NMyIM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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.
--
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 to make pwm_P8_13 low on boot?
- after power on the logic level on P8_13 is low (as I want it to be) - after that (loading dtc overlay) the logic level on P8_13 become high (I dont want it) Sorry, I missed this. The 74HC04 would work if it started high and stayed that way. Do you need to use an overlay? Maybe if you modified the initial device tree, perhaps with Roberts system for the 3.14 kernel it would start high and you could flip it. -- 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 to make pwm_P8_13 low on boot?
The inverter is not a solution as on boot initial pin value is low and after the device tree is loaded it jumps high until the application software (controlling pwm) takes over. I will use it as a temporary solution. Cheers Jan On Wednesday, 26 November 2014 08:45:34 UTC+11, Jason Lange wrote: - after power on the logic level on P8_13 is low (as I want it to be) - after that (loading dtc overlay) the logic level on P8_13 become high (I dont want it) Sorry, I missed this. The 74HC04 would work if it started high and stayed that way. Do you need to use an overlay? *Maybe if you modified the initial device tree, perhaps with Roberts system for the 3.14 kernel it would start high and you could flip it.* http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb -- 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 do I mount rootfs instead of fatfs with g_multi?
Hello All, At one point I accidentally had the root filesystem mounting and perusable from my desktop file browser -- which was useful to me (unlike the fatfs). I am trying to duplicate this deliberately, but can't find where to configure this. Any help with this is much appreciated...my google-fu is failing me. Thanks in advance. j. -- 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] How do I mount rootfs instead of fatfs with g_multi?
Thank you Robert. Are there any caveats to erasing the fatfs and resizing rootfs ? And if I did that would your script mount rootfs without modification? -- 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] How do I mount rootfs instead of fatfs with g_multi?
I took the risk. Since it was on an sd card I popped it out and used gparted to erase the fatfs and then resize rootfs (leaving that holiest of 1M holes). I booted fine except for: [ 15.517979] g_multi musb-hdrc.0.auto: failed to start g_multi: -2 'mount' shows: /dev/mmcblk0p2 on / type ext4 (rw,noatime,errors=remount-ro,data=ordered) ...it's still calling itself partition 2, which is probably a good thing since /etc/fstab is referring to it by its /dev entry So now I'm going to figure out how to re-enumerate the partition and change the fstab entry accordingly. But, I'm hoping to be able to use this card to flash eMMC and now I'm wondering if all this is going to break your scripts? On Tue, Nov 25, 2014 at 6:50 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Nov 25, 2014 at 8:43 PM, Jason Lange j.b.la...@gmail.com wrote: Thank you Robert. Are there any caveats to erasing the fatfs and resizing rootfs ? And if I did that would your script mount rootfs without modification? Well... in theory with the newer images that should still work.. The big (and i mean big) issue, the u-boot (MLO/u-boot.img) files where dd'ed below the 1Mb position. So as long as you leave the 1MB hole at the start of the drive alone, it 'should' work.. 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. -- 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] How do I mount rootfs instead of fatfs with g_multi?
I managed to change the partition number ...and g_multi is serving up my rootfs as pretty as a peach. The odd thing is that I forgot to modify /etc/fstab and it still mounted (?) mount gives me: /dev/mmcblk0p1 on / type ext4 (rw,noatime,errors=remount-ro,data=ordered) ^^^ cat /etc/fstab gives this line: /dev/mmcblk0p2 / ext4 noatime,errors=remount-ro 0 1 ^^^ ...odd. -- 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] Loading custom capes on Debian
What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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. -- 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] Loading custom capes on Debian
I don't have much experience with device tree overlays so I might not be able to help, but what is the exact command you are using to echo it into the slot? On Mon, Nov 24, 2014 at 12:24 AM, Bremenpl breme...@gmail.com wrote: root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone64 #1 SMP Thu Aug 21 21:24:58 UTC 2014 armv7l GNU/Linux W dniu 2014-11-24 o 09:20, Jason Lange pisze: What kernel are you using? (what is the output from uname -a ?) On Mon, Nov 24, 2014 at 12:11 AM, bremenpl breme...@gmail.com wrote: Hello there, I am suing bbb and a Debian Console image. I am strying to locate the place where the tree overlays are located but I cant. I tried greping for BB-UART1 for example but I cant find it. Even though I can export it to slots. I have added my custom cape to /lib/firmware/ but when I try to export it to slots it cannot find the file. In the regular image all tree-overlays are stotred in /lib/firmware/ and in my image that folder is empty. I would really aprichiate any help, this is very urgent for me and I dont have much time :( -- 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. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/DwM-75kDnRc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Bremenpl -- 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. -- 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] Change I2C bus for video communication
I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# 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-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN You have disabled the HDMI overlays, if they were loaded the relevant slots (5 and 6) would start with ff:P-O-L as it does for slot 4. (I believe the L stands for Loaded) -- 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] Change I2C bus for video communication
If you want to load a custom cape at boot you need to follow these instructions: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes On Mon, Nov 24, 2014 at 1:46 AM, Jason Lange j.b.la...@gmail.com wrote: I am not sure if I turned off the standard HDMI overlay, I just commented the enables lines in uEnv.txt, now my slots file looks like this: root@beaglebone:/sys/devices/bone_capemgr.9# 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-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN You have disabled the HDMI overlays, if they were loaded the relevant slots (5 and 6) would start with ff:P-O-L as it does for slot 4. (I believe the L stands for Loaded) -- 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] Change I2C bus for video communication
On Mon, Nov 24, 2014 at 1:52 AM, Bremenpl breme...@gmail.com wrote: In that case after the disabling I have enabled my module by hand (BB-BONELT-HDMIN1): root@beaglebone:~# cat /sys/devices/bone_capemgr.9/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-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONELT-HDMIN1 But i still get no visual on the attached monitor :(. The monitor is in standby so he doesnt get any signal. :( I wish you the best of luck. It's 2am here so I'm going to bed. -- 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] Beaglebone Black Rebooting Several Times Every Day
On Fri, Sep 12, 2014 at 9:35 AM, Robert Nelson robertcnel...@gmail.com wrote: On Fri, Sep 12, 2014 at 11:27 AM, Greg Kelley suekkel...@gmail.com wrote: Robert, I think part of the reason ntp and dhcpclient aren't getting network connections at boot is because they are set at S03 in init and wicd is set at S06 and is last to get going. It appears that eth0 is not coming up until wicd loads? Correct, wicd set's up eth0, that's how we got the 11-12 second bootup time. Otherwise if eth0 is handled by /etc/network/interfaces bootup could last 2 minutes for users who don't connect eth0. I should atleast really move ntp from S03 to S06.. @Robert There's no need to pull in wicd to solve this; all you need to do is to replace auto eth0 with allow-hotplug eth0 (not both) in /etc/network/interfaces. This gives you eth0 at boot if it's plugged in but it doesn't wait if it's not, and if you plug it in later it comes right up. Oddly it doesn't even wait very long if it's plugged in at start-up and there is no dhcp being offered. (all of this is assuming iface eth0 inet dhcp is in there too; I imagine a static route comes up right away regardless.) Cheers. -- 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] Kernel Panic with eMMC flasher
On Mon, Nov 17, 2014 at 1:47 PM, Joe Spanier prcdsln...@gmail.com I am properly ejecting the card from my laptop after completing dd. Is that what you mean by sync? Here are the steps Im using: 1. Wget the image 2. md5sum check 3. xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc change step 3 to: . xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc; sync sync ensures that whatever is in the buffers actually gets written to the disk. The sdcard shouldn't even be mounted on the desktop while you dd it. At least with unity it will still dd properly but the desktop is not aware and shows it mounted in it's previous state. A desktop unmount at this point is potentially harmful. I wish there was a simple way to verify the image after you've flashed it to the card -- does anyone know how to do this? Cheers. -- 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] Kernel Panic with eMMC flasher
On Tue, Nov 18, 2014 at 4:57 PM, William Hermans yyrk...@gmail.com wrote: All you can do is: write data remove media. sync. write data sync and then remove media. That's all I'm really trying to convey. dd does not sync by default. Unmounting from your gui should sync. But might not if you've been sudo-ing things behind it's back. Once sync has completed you can safely remove it regardless of what some gui thinks is going on. -- 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] Kernel Panic with eMMC flasher
On Tue, Nov 18, 2014 at 7:02 PM, William Hermans yyrk...@gmail.com wrote: What I am trying to convey to you is that sync is never guaranteed. Ever. garunteed? -- 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] Kernel Panic with eMMC flasher
twou twou omwee tou twou. ;) On Tue, Nov 18, 2014 at 7:49 PM, Jason Lange j.b.la...@gmail.com wrote: On Tue, Nov 18, 2014 at 7:02 PM, William Hermans yyrk...@gmail.com wrote: What I am trying to convey to you is that sync is never guaranteed. Ever. garunteed? -- 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] Kernel Panic with eMMC flasher
This might not be part of the problem, but I have created much mysterious misery by forgetting to sync after dd-ing my sd card. If you forgot to do this and yanked your card out after dd finished you cannot trust that you have an accurate and functional image. spread the word. On Mon, Nov 17, 2014 at 7:40 AM, Robert Nelson robertcnel...@gmail.com wrote: On Sun, Nov 16, 2014 at 10:41 PM, Joe Spanier prcdsln...@gmail.com wrote: I am trying to flash my eMMC with the image here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases I am using the 4Gb flasher for the RevC. I can flash the microSD but all of the images ive tried cause Kernel Panics when I try to flash the BBB. Im sure this is something I am doing but Im not sure. Here are the steps Im using: 1. Wget the image 2. md5sum check 3. xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc 4. load SD and apply power 5. kernel panic Well 3.8 always panic's (drm) when shutdown at the completion of the flashing procedure. If you have the serial log from the flashing procedure this would confirm that. 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. -- 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] broken sd card reader, need help flashing!!!
I haven't tried this, but it might work for you. https://github.com/ungureanuvladvictor/BBBlfs On Mon, Nov 17, 2014 at 7:02 AM, Gerald Coley ger...@beagleboard.org wrote: SD card is the way we do it. There are other ways, but there is no support for those other ways. Gerald On Sun, Nov 16, 2014 at 10:21 AM, russellne...@gmail.com wrote: ok so i have broken pin 3 on my sd card reader on accident and need to flash my bbb to use my replicape. however i cant seem to find any other method to flash a bbb other than using an sd card. this is kind of depressing considering i dont want to scrap the board because it still works i just cant flash it through the normal sd card method. every bit of help would be appreciated. what i really need is a step by step on how to flash my bbb without an sd card. i have access to ubuntu and win7 64 bit pc. im not a complete noob at this but by no means am i an expert so please go easy on me here. -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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. -- 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] Beaglebone Black Jessie lxqt turn off desktop
This works to turn off lxqt in a running system: sudo systemctl isolate multi-user.target and this starts it up again: sudo systemctl start graphical.target To avoid starting up a graphical desktop at boot run: sudo systemctl set-default multi-user.target and change back with: sudo systemctl set-default graphical.target Cheers. On Mon, Oct 27, 2014 at 10:45 AM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Oct 27, 2014 at 12:42 PM, Peter Gregory talkto...@gmail.com wrote: I'm kicking the tires on Debian 8 jessie on BBB with a 4DCape-43t with the 10/22/2014 lxqt image I've installed SGX and it works great. Is there a way to get it to not load the desktop? In previous versions, you could modify uEnv.txt and add optargs=text And it would boot to a console. Is there a way to do that with this image? Well it's lightdm that triggers lxqt to load, so you could disable that.. 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. -- 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: debian testing: 2014-11-11
...Here's another option I needed to add to dnsmasq.conf: dhcp-option=3 this stops dnsmasq from handing out a default route and screwing up your connection to the internet. On Fri, Nov 14, 2014 at 11:11 PM, Jason Lange j.b.la...@gmail.com wrote: Hi Robert, withThis worked for me: /etc/dnsmasq.conf #disable DNS by setting port to 0 port=0 interface=usb0 dhcp-range=192.168.7.1,192.168.7.1 #one address range /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp allow-hotplug usb0 iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 I'm using your 2014/11/11 jessie image and after I did an apt-get update/upgrade I lost the ability to connect with ssh. removing udhcpd and adding the above configuration for dnsmasq restored my ability to connect via ssh on both interfaces. On Thu, Nov 13, 2014 at 4:06 PM, Robert Nelson robertcnel...@gmail.com wrote: Sure, as long as we can configure dnsmasq to do the work of udhcpd, i'm all for it.. ;) https://wiki.debian.org/HowTo/dnsmasq /etc/dnsmasq.conf dhcp-range=usb0,192.168.7.1,192.168.7.3,12h look sane? 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. -- 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: debian testing: 2014-11-11
Hi Robert, withThis worked for me: /etc/dnsmasq.conf #disable DNS by setting port to 0 port=0 interface=usb0 dhcp-range=192.168.7.1,192.168.7.1 #one address range /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp allow-hotplug usb0 iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 I'm using your 2014/11/11 jessie image and after I did an apt-get update/upgrade I lost the ability to connect with ssh. removing udhcpd and adding the above configuration for dnsmasq restored my ability to connect via ssh on both interfaces. On Thu, Nov 13, 2014 at 4:06 PM, Robert Nelson robertcnel...@gmail.com wrote: Sure, as long as we can configure dnsmasq to do the work of udhcpd, i'm all for it.. ;) https://wiki.debian.org/HowTo/dnsmasq /etc/dnsmasq.conf dhcp-range=usb0,192.168.7.1,192.168.7.3,12h look sane? 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. -- 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] Physically removing the HDMI Frame buffer chip
BlueSteel might be suitable as well: http://www.cnx-software.com/2014/06/18/bluesteel-basic-beaglebone-black/ On Thu, Nov 13, 2014 at 10:36 AM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Nov 13, 2014 at 12:42 AM, promothe...@gmail.com wrote: I would like to physically remove some unused hardware component for testing. Is it possible to remove the HDMI Frame buffer chip without preventing the OS to load? There are lots of expensive components on the board made for most people, others like myself love the board but would have liked other component (JTAG headers) right on there. Did anyone remove this particular chip from their design? The beaglebone (white) does not have the hdmi framer and has a built-in usb-jtag. Based on your comments, it would be an obvious choice.. 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. -- 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: Only able to read 0x0 or FF with spidev...
The two devices that show up are associated with the same clock and data lines, they just have different chip select lines to allow you to multiplex two devices -- they cannot be used simultaneously. On Mon, Nov 10, 2014 at 3:54 PM, janszymanski12...@gmail.com wrote: Hi, Following the links: http://elinux.org/BeagleBone_Black_Enable_SPIDEV and http://www.nagavenkat.adurthi.com/2014/02/spi-communication-beaglebone-black-as-master-to-arduino-as-slave/ I was able to make it work, but I have a SS too long (1.4ms) for my need. For easy test connect MOSI and MISO with a wire (loopback) to eliminate connection problem with you SPI slave. Hope this will help. When you done, can you measure the timing a let me know? I can post you my code if you need it. Jan On Tuesday, November 11, 2014 5:03:38 AM UTC+11, lambert...@gmail.com wrote: Hi, I am trying to communicate with a device (ADS1299à by using the Beaglebone black but without success. First I have to enable spi dev entries in /dev. There are plenty of blog/tuto which are giving dtc file to generate our own dtbo. But dtc files seems to not be always the same. In fact I can see that there are already some dtbo files in /lib/firmware : root@beaglebone:~# ls /lib/firmware/ | grep SPI ADAFRUIT-SPI0-00A0.dtbo ADAFRUIT-SPI1-00A0.dtbo BB-SPIDEV0-00A0.dtbo BB-SPIDEV1-00A0.dtbo BB-SPIDEV1A1-00A0.dtbo So I want to use only SPI0 because I know that SPI1 is already used by HDMI. Can I used theses dtbo files ? Is it better to write my own ? It is quite strange, when I enable one of theses dtbo files, I get not only one but two entries in /dev ?? Currently I want to validate my wiring between the two boards. I found a piece of code to read the device id in register of the device though SPI. But when I try to read this register, I can only get 1 or only get 0 (depends of the dtbo files) Any advice of the good way to process here ? Thanks Regards, Arthur. -- 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. -- 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: Only able to read 0x0 or FF with spidev...
...so if you enable both spidevs you have four devices show up. On Tue, Nov 11, 2014 at 9:51 AM, Jason Lange j.b.la...@gmail.com wrote: The two devices that show up are associated with the same clock and data lines, they just have different chip select lines to allow you to multiplex two devices -- they cannot be used simultaneously. On Mon, Nov 10, 2014 at 3:54 PM, janszymanski12...@gmail.com wrote: Hi, Following the links: http://elinux.org/BeagleBone_Black_Enable_SPIDEV and http://www.nagavenkat.adurthi.com/2014/02/spi-communication-beaglebone-black-as-master-to-arduino-as-slave/ I was able to make it work, but I have a SS too long (1.4ms) for my need. For easy test connect MOSI and MISO with a wire (loopback) to eliminate connection problem with you SPI slave. Hope this will help. When you done, can you measure the timing a let me know? I can post you my code if you need it. Jan On Tuesday, November 11, 2014 5:03:38 AM UTC+11, lambert...@gmail.com wrote: Hi, I am trying to communicate with a device (ADS1299à by using the Beaglebone black but without success. First I have to enable spi dev entries in /dev. There are plenty of blog/tuto which are giving dtc file to generate our own dtbo. But dtc files seems to not be always the same. In fact I can see that there are already some dtbo files in /lib/firmware : root@beaglebone:~# ls /lib/firmware/ | grep SPI ADAFRUIT-SPI0-00A0.dtbo ADAFRUIT-SPI1-00A0.dtbo BB-SPIDEV0-00A0.dtbo BB-SPIDEV1-00A0.dtbo BB-SPIDEV1A1-00A0.dtbo So I want to use only SPI0 because I know that SPI1 is already used by HDMI. Can I used theses dtbo files ? Is it better to write my own ? It is quite strange, when I enable one of theses dtbo files, I get not only one but two entries in /dev ?? Currently I want to validate my wiring between the two boards. I found a piece of code to read the device id in register of the device though SPI. But when I try to read this register, I can only get 1 or only get 0 (depends of the dtbo files) Any advice of the good way to process here ? Thanks Regards, Arthur. -- 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. -- 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: optargs in kernel 3.15.10-bone8
For the sake of future readers (with their googley eyes) it would be nice
if someone (aka robert sea nelson the glorious inland mariner who makes it
possible for us to have all of our problems with his ever changing maps ;)
) piped in come Minnesota Monday Morning (aka M.M.M) and told me how many
times the thing called uEnv.txt is invoked and why he is leaving multiple
copies of it lying around.
On Mon, Sep 8, 2014 at 3:40 AM, William Hermans yyrk...@gmail.com wrote:
Ok, silly me, was editing the wrong file. I was editing the file on the
NFS rootfs, when I am actually loading my second stage uEnv.txt file from
the sdcard.
root@arm:~# mount /dev/mmcblk0p1 /media/boot/
root@arm:~# mkdir /media/rootfs
root@arm:~# mount /dev/mmcblk0p2 /media/rootfs/
root@arm:~# cat /media/boot/uEnv.txt |optargs=
*/* No output now since i completely removed the line */*
root@arm:~# cat /media/rootfs/boot/uEnv.txt
uname_r=3.8.13-bone64.1
cmdline=quiet init=/lib/systemd/systemd consoleblank=0
cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
root@arm:~# cat /sys/module/kernel/parameters/consoleblank
0
Moscowbob, if you're familiar with C I can link you to the header file
that pretty much determines how all this works. The netargs line I am
talking about is something I have set in my own 1st stage uEnv.txt file,
since this used to be the way it had to be done. Now, I use it still,
because I boot custom compared to Roberts new way. I only load the root
file system via NFS, and the kernel still gets loaded from the sdcard.
Understanding all of this takes time. I first learned this around 14-15
months ago when the A5A was first released to the general public. I more
than 2 weeks reading all the uEnv.txt files I could, and when I felt I
understood things well enough, I asked Robert C Nelson a question ( I do
not remember what offhand ), and he linked me to this file.
http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;hb=HEAD#l57
This was enough information for me to fully understand what I needed to do
in order to get what I wanted to achieve done.
Other than this, I do not know how else to explain to you it all works.
Except, if you examine the 1st stage uEnv.txt file I pasted above closer
towards the top, and examine the output of /proc/cmdline . . . It might all
start making sense to you.
On Mon, Sep 8, 2014 at 3:17 AM, William Hermans yyrk...@gmail.com wrote:
Moscowbob, you and I both now. Initially it worked, but now for some
reason it does not. There are a few things I can check and instead of me
doing a play by play and posting 500 lines more . . . let me see if i can
get to the bottom of it.
On Mon, Sep 8, 2014 at 3:12 AM, Moscowbob moscow...@gmail.com wrote:
Sorry - there is a typo..
.the display is now not blanking, after adding the optargs to
uEnv.txt in the fat boot partition but for learning sake, I would like to
know how to achieve this in the /boot/uEnv.txt
On Monday, 8 September 2014 11:08:35 UTC+1, Moscowbob wrote:
Thanks William, but the line in red is just commented out to indicate
it is not part of the working file. I did not work without the hash.
I have followed these instructions http://elinux.
org/Beagleboard:U-boot_partitioning_layout_2.0#nfs_support and there
is no mention of any netargs..
Apologies for my ignorance, but I am brand new to all this and having a
hard time following, would you please clarify how to achieve what you
mentioned.
the display is now not balnking after adding the optargs to uEnv.txt in
the fat boot partition but for learning sake, I would like to know how to
achieve this in the /boot/uEnv.txt
Thanks for the help.
Rob
On Monday, 8 September 2014 10:12:14 UTC+1, William Hermans wrote:
*#cmdline=quiet init=/lib/systemd/systemd consoleblank=0 ===
DOES NOT WORK*
That would be because you need to remove the comment . . .remove the
hash mark or '#'. If that does not work, then your netargs do not contain
${cmdline}
On Mon, Sep 8, 2014 at 1:20 AM, Moscowbob mosc...@gmail.com wrote:
Thank you all for you assistance the problem is resolved. just some
additional points.
SD Card boot partition:
uEnv.txt
##Rename as: uEnv.txt to boot via nfs
##https://www.kernel.org/doc/Documentation/filesystems/nfs/
nfsroot.txt
##SERVER: sudo apt-get install tftpd-hpa
##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa
##SERVER: zImage/*.dtb need to be located here:
##SERVER: TFTP_DIRECTORY/zImage
##SERVER: TFTP_DIRECTORY/dtbs/*.dtb
##client_ip needs to be set for u-boot to try booting via nfs
client_ip=192.168.1.17
#u-boot defaults: uncomment and override where needed
server_ip=192.168.1.12
gw_ip=192.168.1.1
netmask=255.255.255.0
#hostname=
device=eth0
#autoconf=off
root_dir=/home/rob/beaglebone/rootfs
nfs_options=,vers=3
nfsrootfstype=ext4 rootwait fixrtc
*optargs=consoleblank=0*
Re: [beagleboard] Arduino to Beaglebone serial connection
This might not be your problem, but it's important that both boards share a common ground. The picture shown on the link you've given is missing a wire. The two blue wires shown at the end of the breadboard are meant to be connecting the two ground rails but don't as there is no wire bridging the gap in the middle of the breadboard. You can bridge that gap or just use a longer wire that goes from ground rail to ground rail (or arduino gnd to beagle gnd directly). Many protocols (like rs-422, rs-485, ethernet, usb, etc.) use a differential signal to allow communication even if grounds are floating relative to each other but ordinary uarts and spi are completely unreliable without tying ground potential together. On Sat, Sep 6, 2014 at 8:09 PM, m34tc...@gmail.com wrote: I am trying to enable serial communication between an arduino and beaglebone black, for a home automation system. I got it working once(the beaglebone printed data it was receiving) but hasn't worked since. I followed this http://www.instructables.com/id/How-to-make-a-BeagleBone-and-an-Arduino-communicat/ guide. My only thought is maybe somehow the Serial4 pins became damaged? If so, how could I test the Beaglebones RX. Using another serial port is an option, although I don't know how to use them. -- 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. -- 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: optargs in kernel 3.15.10-bone8
On Mon, Sep 8, 2014 at 4:25 AM, Robert Nelson robertcnel...@gmail.com wrote: u-boot older then: v2014.07 (with my patch) /uEnv.txt (in fat partition) loads /boot/uEnv.txt (in ext4 partition) u-boot newer then: v2014.07 (with my patch) u-boot finds /boot/uEnv.txt in any partition (1 - 7) Regards, So, the ext4 /uEnv.txt is just cruft? -- 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: optargs in kernel 3.15.10-bone8
Thanks Robert. Just to be clear, with my currant set up (one ext4 eMMC partition only) the only uEnv.txt that is being used is /boot/uEnv.txt, and the /uEnv.txt is not functional? But if it was on an SD card and was inserted into a board that had been flashed with Angstrom the /uEnv.txt would allow the SD card to boot? Even as an SD card with ext4 only? If the above is true, would my /boot/uEnv.txt be seen at all? (that is booting from the SD card on an Angstrom flashed board) On Mon, Sep 8, 2014 at 6:36 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Sep 8, 2014 at 8:22 PM, Jason Lange j.b.la...@gmail.com wrote: On Mon, Sep 8, 2014 at 4:25 AM, Robert Nelson robertcnel...@gmail.com wrote: u-boot older then: v2014.07 (with my patch) /uEnv.txt (in fat partition) loads /boot/uEnv.txt (in ext4 partition) u-boot newer then: v2014.07 (with my patch) u-boot finds /boot/uEnv.txt in any partition (1 - 7) Regards, So, the ext4 /uEnv.txt is just cruft? If the ext4 is the only partition the /uEnv.txt is there for old boot-loaders. Basically, my goal is to stay compatible with Angstrom's 2013.06.20 release. My images should boot from microSD if the Angstrom 2013.06.20 release is flashed to eMMC.. Between last week's release and the July one, we had regressed on that goal. But we got those bugs worked out.. u-boot's actually searching for a few different boot files 1: microsd: Partition 1: /uEnv.txt /boot.scr /boot/boot.scr Parition 1-7 /boot/uEnv.txt 2: eMMC Partition 1: /uEnv.txt /boot.scr /boot/boot.scr Parition 1-7 /boot/uEnv.txt I've also been adding lots of debugging info to u-boot to help users hints: (here's my current wip off v2014.10-rc2, the last two debug lines before the kernel goes off should really help users..) mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 Checking for: /uEnv.txt ... Checking for: /boot.scr ... Checking for: /boot/boot.scr ... Checking for: /boot/uEnv.txt ... gpio: pin 55 (gpio 55) value is 1 799 bytes read in 53 ms (14.6 KiB/s) Loaded environment from /boot/uEnv.txt Checking if uname_r is set in /boot/uEnv.txt... gpio: pin 56 (gpio 56) value is 1 Running uname_boot ... loading /boot/vmlinuz-3.14.17-ti-r18.1 ... 6937752 bytes read in 438 ms (15.1 MiB/s) loading /boot/dtbs/3.14.17-ti-r18.1/am335x-boneblack.dtb ... 64941 bytes read in 119 ms (532.2 KiB/s) debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait fixrtc quiet] ... debug: [bootz 0x8200 - 0x8800] ... Kernel image @ 0x8200 [ 0x00 - 0x69dc98 ] ## Flattened Device Tree blob at 8800 Booting using the fdt blob at 0x8800 Loading Device Tree to 8ffed000, end 8dac ... OK Starting kernel ... 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. -- 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] optargs in kernel 3.15.10-bone8
On Sun, Sep 7, 2014 at 8:35 PM, William Hermans yyrk...@gmail.com wrote: Jason, hah ! I see why now. Can you see the problem ? *uname_r=3.15.10-bone8* *cmdline=quiet init=/lib/systemd/systemd* *optargs=consoleblank=0*. This is actually in the wrong file. For this to work in the file he's using there it needs to be as i said above. Which is: *cmdline=quiet init=/lib/systemd/systemd* *consoleblank=0* This is because the file he's using is the second stage uEnv.txt file and not the one loaded at boot. Which now that I think about it could have very well been my problem too. Well I finally understand what your saying here -- I didn't know that there are/were two functional uEnv.txt*s*. This looks like the file that I set my optargs in (that is, it starts with the uname_r variable being set), but I am running the new set up with only one uEnv.txt being functional. @Robert again for clarity: In a setup that only uses one uEnv.txt (that being /boot/uEnv.txt) that is the place to set your optargs but in the two functional uEnv.txt setup the place to set optargs is /uEnv.txt? And if that is so, what is the simplest way for someone to know which of the two situations they are dealing with? -- 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] optargs in kernel 3.15.10-bone8
Sorry, I don't want to shut you down. It just seemed like a natural break
in a long thread. (If there was a sideband I wouldn't be tacking this on.)
Cheers William.
On Mon, Sep 8, 2014 at 10:05 PM, William Hermans yyrk...@gmail.com wrote:
um If you posts on this subject are valid so are mine. A/B conversation
as well.
On Mon, Sep 8, 2014 at 10:01 PM, Jason Lange j.b.la...@gmail.com wrote:
ummn... new topic?
On Mon, Sep 8, 2014 at 9:59 PM, William Hermans yyrk...@gmail.com
wrote:
Robert, using your build instructions and compiling the kernel from
source ( 3.8.13-bone64.1 ) it is somehow loading omap_rng module at boot.
IS this normal, or did i somehow screw up in menuconfig ?
As it is, I have the module blacklisted, but I'd rather it did not exist
at all on my own system.
Also, I'm looking into building that html5 web app you say you're
waiting for. Anything specific you want ? Or just so long as it executes
the commands mentioned above ?
On Mon, Sep 8, 2014 at 9:42 PM, Jason Lange j.b.la...@gmail.com wrote:
Too much fun!
On Mon, Sep 8, 2014 at 9:32 PM, William Hermans yyrk...@gmail.com
wrote:
Jason, he was using a console testing image, and using the built in
env variables for tftp + nfs. These images came with two uEnv.txt files,
and since he was having problems with uboot env variables I'm betting he
actually had 3 uEnv.txt files.
1) fat / boot part
2) ext4 footfs on sdcard
3) ext4 rootfs on nfs share host.
uboot was probably pulling in the uEnv.txt which he was not editing.
Which again, I'm betting was on partition 2 ( ext4 ) of the sdcard. e.g.
he
was editing the uEnv.txt file on the nfs share as I suggested.
On Mon, Sep 8, 2014 at 9:04 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange j.b.la...@gmail.com
wrote:
On Sun, Sep 7, 2014 at 8:35 PM, William Hermans yyrk...@gmail.com
wrote:
Jason, hah ! I see why now. Can you see the problem ?
uname_r=3.15.10-bone8
cmdline=quiet init=/lib/systemd/systemd
optargs=consoleblank=0.
This is actually in the wrong file. For this to work in the file
he's
using there it needs to be as i said above. Which is:
cmdline=quiet init=/lib/systemd/systemd consoleblank=0
This is because the file he's using is the second stage uEnv.txt
file and
not the one loaded at boot. Which now that I think about it could
have very
well been my problem too.
Well I finally understand what your saying here -- I didn't know
that there
are/were two functional uEnv.txts. This looks like the file that I
set my
optargs in (that is, it starts with the uname_r variable being
set), but I
am running the new set up with only one uEnv.txt being functional.
@Robert again for clarity:
In a setup that only uses one uEnv.txt (that being /boot/uEnv.txt)
that is
the place to set your optargs but in the two functional uEnv.txt
setup the
place to set optargs is /uEnv.txt?
Just edit:
/boot/uEnv.txt
/uEnv.txt is just a shim..
And if that is so, what is the simplest way for someone to know
which of the
two situations they are dealing with?
/uEnv.txt will set your bootargs like so:
setenv bootargs console=tty0 console=\${console} \${optargs}
\${cape_disable} \${cape_enable} root=/dev/mmcblk0p1
rootfstype=\${mmcrootfstype} \${cmdline}
So override any of those \${var} by defining them in /boot/uEnv.txt
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.
--
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.
--
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.
--
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.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
Re: [beagleboard] optargs in kernel 3.15.10-bone8
Hi again, I just tried wrapping my optarg in quotes and it didn't make a lick of difference, so that's not it. It's seems that I should have the latest uboot since I'm running an image from 3 days ago. My optargs aren't broken. On Sun, Sep 7, 2014 at 7:36 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:26 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 optargs does not work in the latest uboot file setup. I've noticed this myself in othe situations. you have to use Robert new cmdline env variable https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch Looking at the u-boot patch it looks like optargs is used with both mmcargs and nfsargs. Regards, John On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange j.b.la...@gmail.com wrote: Hello, I'm wondering if it would help if you changed from: optargs=consoleblank=0 to: optargs=consoleblank=0 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian Image 2014-09-04 running 3.14.17-ti-r17 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans yyrk...@gmail.com wrote: @Robert I'll have you know that you've broken $optargs in the initial stage uEnv.txt. In case you did not know already . . . On Sun, Sep 7, 2014 at 6:32 PM, William Hermans yyrk...@gmail.com wrote: hmm so actual that did not work for me either, which I do not know is a bug or what so here is what I had to do. First check output of: *$ cat /sys/module/kernel/parameters/consoleblank* *600* It'll probably be 600 as above, which is ten minutes( 600 seconds ). So . . . *nano /boot/uEnv.txt* and uncomment this line: *#cmdline=quiet init=/lib/systemd/systemd* then add at the end *consoleblank=0* Which gives you *cmdline=quiet init=/lib/systemd/systemd consoleblank=0* reboot the beaglebone and when it comes back up. *root@arm:~# cat /sys/module/kernel/parameters/consoleblank* *0* On Sun, Sep 7, 2014 at 6:07 PM, William Hermans yyrk...@gmail.com wrote: errr sorry, that should only be *setterm -blank 0* On Sun, Sep 7, 2014 at 6:03 PM, William Hermans yyrk...@gmail.com wrote: $ setterm -powersave off -blank 0 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob moscow...@gmail.com wrote: BBB boot from tftp and nfs - kernel: 3.15.10-bone8 rootfs: debian-jessie-console-armhf-2014-08-13 Hardware: BBB A5C Circuitco LCD4 cape Circuitco RS232 cape /home/rob/rootfs/boot/uEnv.txt uname_r=3.15.10-bone8 cmdline=quiet init=/lib/systemd/systemd *optargs=consoleblank=0*. I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F but the display is still blanking after 10 minutes. Would appreciate some guidance. Thanks Rob -- 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. -- 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. -- 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. -- 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. -- 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. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group
Re: [beagleboard] optargs in kernel 3.15.10-bone8
try: cat /proc/cmdline to see if optargs show there On Sun, Sep 7, 2014 at 7:46 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:43 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 Ok, so rather coming in and sniping a comment Jjohn, why dont you try and set an optargs env variable in the initial uEnv.txt file and see what happens. If you're using the same uboot we're using, it wont work. Now, feel free to find yourself trolling a different post. Wow, that was so unnecessary. I was just trying to be helpful. Regards, John On Sun, Sep 7, 2014 at 7:36 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:26 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 optargs does not work in the latest uboot file setup. I've noticed this myself in othe situations. you have to use Robert new cmdline env variable https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch Looking at the u-boot patch it looks like optargs is used with both mmcargs and nfsargs. Regards, John On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange j.b.la...@gmail.com wrote: Hello, I'm wondering if it would help if you changed from: optargs=consoleblank=0 to: optargs=consoleblank=0 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian Image 2014-09-04 running 3.14.17-ti-r17 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans yyrk...@gmail.com wrote: @Robert I'll have you know that you've broken $optargs in the initial stage uEnv.txt. In case you did not know already . . . On Sun, Sep 7, 2014 at 6:32 PM, William Hermans yyrk...@gmail.com wrote: hmm so actual that did not work for me either, which I do not know is a bug or what so here is what I had to do. First check output of: *$ cat /sys/module/kernel/parameters/consoleblank* *600* It'll probably be 600 as above, which is ten minutes( 600 seconds ). So . . . *nano /boot/uEnv.txt* and uncomment this line: *#cmdline=quiet init=/lib/systemd/systemd* then add at the end *consoleblank=0* Which gives you *cmdline=quiet init=/lib/systemd/systemd consoleblank=0* reboot the beaglebone and when it comes back up. *root@arm:~# cat /sys/module/kernel/parameters/consoleblank* *0* On Sun, Sep 7, 2014 at 6:07 PM, William Hermans yyrk...@gmail.com wrote: errr sorry, that should only be *setterm -blank 0* On Sun, Sep 7, 2014 at 6:03 PM, William Hermans yyrk...@gmail.com wrote: $ setterm -powersave off -blank 0 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob moscow...@gmail.com wrote: BBB boot from tftp and nfs - kernel: 3.15.10-bone8 rootfs: debian-jessie-console-armhf-2014-08-13 Hardware: BBB A5C Circuitco LCD4 cape Circuitco RS232 cape /home/rob/rootfs/boot/uEnv.txt uname_r=3.15.10-bone8 cmdline=quiet init=/lib/systemd/systemd *optargs=consoleblank=0*. I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F but the display is still blanking after 10 minutes. Would appreciate some guidance. Thanks Rob -- 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. -- 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. -- 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. -- 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
Re: [beagleboard] optargs in kernel 3.15.10-bone8
just added fauxarg to my optargs like this: optargs=spidev.bufsiz=16384 fauxarg and rebooted. Now cat /proc/cmdline shows this: console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg* root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd On Sun, Sep 7, 2014 at 7:51 PM, William Hermans yyrk...@gmail.com wrote: Since both of you seem convinced that optargs is not broken, why dont you actually go make changes to your own uEnv.txt and test if what you think will work, actually works. What I did works, as I tested it myself. On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange j.b.la...@gmail.com wrote: try: cat /proc/cmdline to see if optargs show there On Sun, Sep 7, 2014 at 7:46 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:43 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 Ok, so rather coming in and sniping a comment Jjohn, why dont you try and set an optargs env variable in the initial uEnv.txt file and see what happens. If you're using the same uboot we're using, it wont work. Now, feel free to find yourself trolling a different post. Wow, that was so unnecessary. I was just trying to be helpful. Regards, John On Sun, Sep 7, 2014 at 7:36 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:26 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 optargs does not work in the latest uboot file setup. I've noticed this myself in othe situations. you have to use Robert new cmdline env variable https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch Looking at the u-boot patch it looks like optargs is used with both mmcargs and nfsargs. Regards, John On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange j.b.la...@gmail.com wrote: Hello, I'm wondering if it would help if you changed from: optargs=consoleblank=0 to: optargs=consoleblank=0 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian Image 2014-09-04 running 3.14.17-ti-r17 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans yyrk...@gmail.com wrote: @Robert I'll have you know that you've broken $optargs in the initial stage uEnv.txt. In case you did not know already . . . On Sun, Sep 7, 2014 at 6:32 PM, William Hermans yyrk...@gmail.com wrote: hmm so actual that did not work for me either, which I do not know is a bug or what so here is what I had to do. First check output of: *$ cat /sys/module/kernel/parameters/consoleblank* *600* It'll probably be 600 as above, which is ten minutes( 600 seconds ). So . . . *nano /boot/uEnv.txt* and uncomment this line: *#cmdline=quiet init=/lib/systemd/systemd* then add at the end *consoleblank=0* Which gives you *cmdline=quiet init=/lib/systemd/systemd consoleblank=0* reboot the beaglebone and when it comes back up. *root@arm:~# cat /sys/module/kernel/parameters/consoleblank* *0* On Sun, Sep 7, 2014 at 6:07 PM, William Hermans yyrk...@gmail.com wrote: errr sorry, that should only be *setterm -blank 0* On Sun, Sep 7, 2014 at 6:03 PM, William Hermans yyrk...@gmail.com wrote: $ setterm -powersave off -blank 0 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob moscow...@gmail.com wrote: BBB boot from tftp and nfs - kernel: 3.15.10-bone8 rootfs: debian-jessie-console-armhf-2014-08-13 Hardware: BBB A5C Circuitco LCD4 cape Circuitco RS232 cape /home/rob/rootfs/boot/uEnv.txt uname_r=3.15.10-bone8 cmdline=quiet init=/lib/systemd/systemd *optargs=consoleblank=0*. I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F but the display is still blanking after 10 minutes. Would appreciate some guidance. Thanks Rob -- 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. -- 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. -- For more options, visit
Re: [beagleboard] optargs in kernel 3.15.10-bone8
I don't know if capemanager is functional for these new fangled kernels. optargs will happily pass non functional arguments (like my fauxarg above). Maybe optargs was passing your capemgr.disable argument and it was something else that was broken? But if you can make it work why isn't it working for MoscowBob ?? On Sun, Sep 7, 2014 at 8:20 PM, William Hermans yyrk...@gmail.com wrote: For the record. in that cmdline *consoleblank=0* is declared in $optargs and *init=/lib/systemd/systemd *is declared in* $cmdline. * Previously I had tried disabling hdmi via optargs, so maybe that is now different. Either way *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN* was not working for me On Sun, Sep 7, 2014 at 8:08 PM, William Hermans yyrk...@gmail.com wrote: Jason, odd, it seems to be working for me now too. Previously the cmdline env variable was overriding my optargs statements. *root@arm:~# cat /sys/module/kernel/parameters/consoleblank* *0* *root@arm:~# cat /proc/cmdline* *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3 rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm quiet init=/lib/systemd/systemd* On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange j.b.la...@gmail.com wrote: just added fauxarg to my optargs like this: optargs=spidev.bufsiz=16384 fauxarg and rebooted. Now cat /proc/cmdline shows this: console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg* root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd On Sun, Sep 7, 2014 at 7:51 PM, William Hermans yyrk...@gmail.com wrote: Since both of you seem convinced that optargs is not broken, why dont you actually go make changes to your own uEnv.txt and test if what you think will work, actually works. What I did works, as I tested it myself. On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange j.b.la...@gmail.com wrote: try: cat /proc/cmdline to see if optargs show there On Sun, Sep 7, 2014 at 7:46 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:43 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 Ok, so rather coming in and sniping a comment Jjohn, why dont you try and set an optargs env variable in the initial uEnv.txt file and see what happens. If you're using the same uboot we're using, it wont work. Now, feel free to find yourself trolling a different post. Wow, that was so unnecessary. I was just trying to be helpful. Regards, John On Sun, Sep 7, 2014 at 7:36 PM, John Syn john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Sunday, September 7, 2014 at 7:26 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8 optargs does not work in the latest uboot file setup. I've noticed this myself in othe situations. you have to use Robert new cmdline env variable https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch Looking at the u-boot patch it looks like optargs is used with both mmcargs and nfsargs. Regards, John On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange j.b.la...@gmail.com wrote: Hello, I'm wondering if it would help if you changed from: optargs=consoleblank=0 to: optargs=consoleblank=0 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian Image 2014-09-04 running 3.14.17-ti-r17 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans yyrk...@gmail.com wrote: @Robert I'll have you know that you've broken $optargs in the initial stage uEnv.txt. In case you did not know already . . . On Sun, Sep 7, 2014 at 6:32 PM, William Hermans yyrk...@gmail.com wrote: hmm so actual that did not work for me either, which I do not know is a bug or what so here is what I had to do. First check output of: *$ cat /sys/module/kernel/parameters/consoleblank* *600* It'll probably be 600 as above, which is ten minutes( 600 seconds ). So . . . *nano /boot/uEnv.txt* and uncomment this line: *#cmdline=quiet init=/lib/systemd/systemd* then add at the end *consoleblank=0* Which gives you *cmdline=quiet init=/lib/systemd/systemd consoleblank=0* reboot the beaglebone and when it comes back up. *root@arm:~# cat /sys/module/kernel/parameters/consoleblank* *0* On Sun, Sep 7, 2014 at 6:07 PM, William Hermans yyrk...@gmail.com wrote: errr sorry, that should only be *setterm -blank 0* On Sun, Sep 7, 2014 at 6:03 PM, William Hermans yyrk...@gmail.com wrote: $ setterm -powersave off -blank 0 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob moscow
[beagleboard] Re: debian testing: 2014-09-03 (goodbye vfat release)
This is good. I really like that when I plug it into my desktop usb port I now have the whole root file system mounting and available for overview from my desktop. So with only a usb connection I can ssh into 192.168.7.2 where I do most of my work but I can still mouse around the file system with a gui overview without the overhead of a desktop running on the BBB. Note: I started with this image : http://rcn-ee.net/deb/testing/2014-09-04/console/bone-debian-7.6-console-armhf-2014-09-04-2gb.img.xz which has just one ext4 partition. No fat. No cholesterol. (console images are anorexic to began with, so I had to force feed it a mass of debs to build up its strength.) I don't know what happens to your gadget functionality if you convert from an existing system Thank you Robert. -- 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] How to enable SPI devices on 3.14 kernel?
On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot ..I think I should add this for completion Also do: #include am335x-boneblack-nxp-hdmi-audio.dtsi to: /*#include am335x-boneblack-nxp-hdmi-audio.dtsi*/ and if you want hdmi do: /* #include am335x-boneblack-nxp-hdmi-no-audio.dtsi*/ to: #include am335x-boneblack-nxp-hdmi-no-audio.dtsi -- 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] How to enable SPI devices on 3.14 kernel?
On Tuesday, 2 September 2014 16:15:58 UTC-7, William Hermans wrote: Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. For a while the fat16 partition was mounted at /boot/uboot so that the kinds of things that frequently go in boot like different kernel images could be kept there without filling up the tiny FAT16 partition (similar to /boot/efi). The factory images from May which are labeled BeagleBoard.org Latest Firmware Images are that way. From /etc/fstab: /dev/mmcblk0p1 /boot/uboot auto defaults0 0. Scripts that manipulate /boot should take this possibility into account. -- 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] How to enable SPI devices on 3.14 kernel?
Hello Robert, I had done just as you've described, but the system I started with had uboot and company installed in /boot/uboot rather than /boot and your 'make install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I guessed that that was why I wasn't seeing the changes I was hoping for ( that is: /dev/spidev2.[0/1] ) so i tried completing the install for my setup by moving files into /boot/uboot/dtbs and bricked my board. This morning I began with: https://rcn-ee.net/deb/testing/2014-08-19/lxde/BBB-eMMC-flasher-debian-7.6-lxde-armhf-2014-08-19-2gb.img.xz flashed my bone... did: apt-get install linux-image-3.14.17-ti-r16 then: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git then changed ../dtb-rebuilder.git/src/arm/am335x-boneblack.dts following your guidelines below: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot The system this gives me has everything in /boot and nothing in /boot/uboot and 'make install' does what it is supposed to, and sure enough after reboot: ls /dev/spidev* gives me: /dev/spidev1.0 /dev/spidev1.1 /dev/spidev2.0 /dev/spidev2.1 Thanks for the time and the tools. -- 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] How to enable SPI devices on 3.14 kernel?
Hello Robert, I've just tried to duplicate your instructions here to get both spidev 0 and 1 using your dts from the pastebin link above and I am only getting /dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N uname -a: Linux SQR-3 3.14.17-ti-r16 #1 SMP Thu Aug 28 23:18:48 UTC 2014 armv7l GNU/Linux I just updated from 3.8 using your latest install-me.sh from rcn-ee.org and did: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git *make* and *make install *did not complain but no joy. On Wednesday, 27 August 2014 19:59:11 UTC-7, Dallas Clement wrote: You're my hero! :) Working like a champ now! Thanks a million. On Wed, Aug 27, 2014 at 9:42 PM, Robert Nelson robert...@gmail.com javascript: wrote: On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement dallas.a...@gmail.com javascript: wrote: I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb Here you go: http://pastebin.com/rSg1h46h (just disabled the last line, proto-cape, as it'll inerfear) 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: Device tree overlays may load manually, but not at boot.
Hello, I've had similar problems, and similar frustration with existing instructions. My workaround was to put this line in /etc/rc.local: /usr/local/bin/startSPI.sh /dev/null I believe that the output redirect and the will prevent this line from hanging initiation if anything goes wrong. But I don't know for sure... (anyone care to comment?) ...and adding a startSPI.sh in /usr/local/bin/ with contents like this: #!/bin/bash echo CUSTOM-SPIDEV0 /sys/devices/bone_capemgr.*/slots echo CUSTOM-SPIDEV1 /sys/devices/bone_capemgr.*/slots exit Note: the shebang line calls /bin/bash not /bin/sh. /bin/sh -- /bin/dash in debian and it didn't like the wild-card * which I believe might be necessary... (anyone care to comment? I hope this is useful. Cheers. On Thursday, 14 August 2014 09:02:32 UTC-7, Terje Froysa wrote: Dear Forum, I have now turned the web outside-in to find an answer to this question. I see a lot of subjects touching the subject, but the answers and suggestions are mostly in the hear-say category and points in different directions putting me off in an endless ghost-hunt. I have been testing various overlays, some loads without problems, other won't load but can be manually loaded after boot. I can even rename an overlay that loads and it stops loading even if the content is identical. I have changed the sequence of loading proving that the file system is ready at the time of loading. I have tested the suggested solutions from: http://elinux.org/BeagleBone_Black_Enable_SPIDEV The .dtbo files does not load at boot, but can be loaded manually later. And working when loaded! The boot log gives no clue of what the problem may be. - Is it the content of the .dtbo? - Is it the name of the .dtbo file? Please advice Best regards Terje Froysa *Running system:* debian@beaglebone:~$ uname -a Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014 armv7l GNU/Linux *Boot log showing BB-SPI1-SWP-01 not loading:* debian@beaglebone:~$ dmesg |grep BB- [ 0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN capemgr.enable_partno=BB-I2C1,BB-SPI1-SWP-01 root=UUID=5a42a22f-1771-4c44-93ef-8879c38b63d9 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd [ 0.565888] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMI [ 0.565937] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMIN [ 0.714324] bone-capemgr bone_capemgr.9: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' [ 0.714439] bone-capemgr bone_capemgr.9: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' [ 0.714540] bone-capemgr bone_capemgr.9: slot #6: 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' [ 0.714612] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-I2C1', version 'N/A', prio '0' [ 0.714653] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,BB-I2C1' [ 0.714725] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-SPI1-SWP-01', version 'N/A', prio '0' [ 0.714762] bone-capemgr bone_capemgr.9: slot #8: 'Override Board Name,00A0,Override Manuf,BB-SPI1-SWP-01' [ 0.714928] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMI [ 0.714943] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMIN [ 0.715135] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715149] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715228] bone-capemgr bone_capemgr.9: loader: before slot-7 BB-I2C1:00A0 (prio 0) [ 0.715240] bone-capemgr bone_capemgr.9: loader: check slot-7 BB-I2C1:00A0 (prio 0) [ 0.715732] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.718442] bone-capemgr bone_capemgr.9: loader: after slot-7 BB-I2C1:00A0 (prio 0) [ 0.718462] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'BB-I2C1-00A0.dtbo [ 0.718477] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'BB-I2C1-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 0.718506] bone-capemgr bone_capemgr.9: slot #7: dtbo 'BB-I2C1-00A0.dtbo' loaded; converting to live tree [ 0.720710] bone-capemgr bone_capemgr.9: loader: before slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720724] bone-capemgr bone_capemgr.9: loader: check slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720740] bone-capemgr bone_capemgr.9: loader: after slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720754] bone-capemgr bone_capemgr.9: slot #8: Requesting part number/version based 'BB-SPI1-SWP-01-00A0.dtbo [ 0.720770] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 'BB-SPI1-SWP-01-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 0.721636]
[beagleboard] Re: Device tree overlays may load manually, but not at boot.
running it manually as root starting with /bin/bash then using vi to change to /bin/sh I get this: root@sqr1 ~ # cd /usr/local/bin root@sqr1 /usr/local/bin # mv startSPI.sh.hid startSPI.sh root@sqr1 /usr/local/bin # ./startSPI.sh root@sqr1 /usr/local/bin # root@sqr1 /usr/local/bin # vi ./startSPI.sh root@sqr1 /usr/local/bin # root@sqr1 /usr/local/bin # ./startSPI.sh ./startSPI.sh: 3: ./startSPI.sh: cannot create /sys/devices/bone_capemgr.*/slots: Directory nonexistent ./startSPI.sh: 4: ./startSPI.sh: cannot create /sys/devices/bone_capemgr.*/slots: Directory nonexistent I don't understand why. On Thursday, 14 August 2014 09:02:32 UTC-7, Terje Froysa wrote: Dear Forum, I have now turned the web outside-in to find an answer to this question. I see a lot of subjects touching the subject, but the answers and suggestions are mostly in the hear-say category and points in different directions putting me off in an endless ghost-hunt. I have been testing various overlays, some loads without problems, other won't load but can be manually loaded after boot. I can even rename an overlay that loads and it stops loading even if the content is identical. I have changed the sequence of loading proving that the file system is ready at the time of loading. I have tested the suggested solutions from: http://elinux.org/BeagleBone_Black_Enable_SPIDEV The .dtbo files does not load at boot, but can be loaded manually later. And working when loaded! The boot log gives no clue of what the problem may be. - Is it the content of the .dtbo? - Is it the name of the .dtbo file? Please advice Best regards Terje Froysa *Running system:* debian@beaglebone:~$ uname -a Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014 armv7l GNU/Linux *Boot log showing BB-SPI1-SWP-01 not loading:* debian@beaglebone:~$ dmesg |grep BB- [ 0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN capemgr.enable_partno=BB-I2C1,BB-SPI1-SWP-01 root=UUID=5a42a22f-1771-4c44-93ef-8879c38b63d9 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd [ 0.565888] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMI [ 0.565937] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMIN [ 0.714324] bone-capemgr bone_capemgr.9: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' [ 0.714439] bone-capemgr bone_capemgr.9: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' [ 0.714540] bone-capemgr bone_capemgr.9: slot #6: 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' [ 0.714612] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-I2C1', version 'N/A', prio '0' [ 0.714653] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,BB-I2C1' [ 0.714725] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-SPI1-SWP-01', version 'N/A', prio '0' [ 0.714762] bone-capemgr bone_capemgr.9: slot #8: 'Override Board Name,00A0,Override Manuf,BB-SPI1-SWP-01' [ 0.714928] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMI [ 0.714943] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMIN [ 0.715135] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715149] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715228] bone-capemgr bone_capemgr.9: loader: before slot-7 BB-I2C1:00A0 (prio 0) [ 0.715240] bone-capemgr bone_capemgr.9: loader: check slot-7 BB-I2C1:00A0 (prio 0) [ 0.715732] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.718442] bone-capemgr bone_capemgr.9: loader: after slot-7 BB-I2C1:00A0 (prio 0) [ 0.718462] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'BB-I2C1-00A0.dtbo [ 0.718477] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'BB-I2C1-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 0.718506] bone-capemgr bone_capemgr.9: slot #7: dtbo 'BB-I2C1-00A0.dtbo' loaded; converting to live tree [ 0.720710] bone-capemgr bone_capemgr.9: loader: before slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720724] bone-capemgr bone_capemgr.9: loader: check slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720740] bone-capemgr bone_capemgr.9: loader: after slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720754] bone-capemgr bone_capemgr.9: slot #8: Requesting part number/version based 'BB-SPI1-SWP-01-00A0.dtbo [ 0.720770] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 'BB-SPI1-SWP-01-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 0.721636] bone-capemgr bone_capemgr.9: loader: done slot-7 BB-I2C1:00A0 (prio 0) [ 0.721672] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[beagleboard] Re: Device tree overlays may load manually, but not at boot.
I found this: *...POSIX says that a non-interactive shell must not generate pathnames for a redirection; an interactive shell may do so, provided there is exactly one match.. * So although: echo BB-SPIDEV0/sys/devices/bone_capemgr.*/slots might work when you are doing it manually, you need to do something like this: #!/bin/sh -e slots=$(ls /sys/devices/bone_capemgr.*/slots) echo BB-SPIDEV0 $slots echo BB-SPIDEV1 $slots exit to make it run in a plain sh script On Friday, 15 August 2014 12:03:36 UTC-7, Jason Lange wrote: running it manually as root starting with /bin/bash then using vi to change to /bin/sh I get this: root@sqr1 ~ # cd /usr/local/bin root@sqr1 /usr/local/bin # mv startSPI.sh.hid startSPI.sh root@sqr1 /usr/local/bin # ./startSPI.sh root@sqr1 /usr/local/bin # root@sqr1 /usr/local/bin # vi ./startSPI.sh root@sqr1 /usr/local/bin # root@sqr1 /usr/local/bin # ./startSPI.sh ./startSPI.sh: 3: ./startSPI.sh: cannot create /sys/devices/bone_capemgr.*/slots: Directory nonexistent ./startSPI.sh: 4: ./startSPI.sh: cannot create /sys/devices/bone_capemgr.*/slots: Directory nonexistent I don't understand why. On Thursday, 14 August 2014 09:02:32 UTC-7, Terje Froysa wrote: Dear Forum, I have now turned the web outside-in to find an answer to this question. I see a lot of subjects touching the subject, but the answers and suggestions are mostly in the hear-say category and points in different directions putting me off in an endless ghost-hunt. I have been testing various overlays, some loads without problems, other won't load but can be manually loaded after boot. I can even rename an overlay that loads and it stops loading even if the content is identical. I have changed the sequence of loading proving that the file system is ready at the time of loading. I have tested the suggested solutions from: http://elinux.org/BeagleBone_Black_Enable_SPIDEV The .dtbo files does not load at boot, but can be loaded manually later. And working when loaded! The boot log gives no clue of what the problem may be. - Is it the content of the .dtbo? - Is it the name of the .dtbo file? Please advice Best regards Terje Froysa *Running system:* debian@beaglebone:~$ uname -a Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014 armv7l GNU/Linux *Boot log showing BB-SPI1-SWP-01 not loading:* debian@beaglebone:~$ dmesg |grep BB- [ 0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN capemgr.enable_partno=BB-I2C1,BB-SPI1-SWP-01 root=UUID=5a42a22f-1771-4c44-93ef-8879c38b63d9 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd [ 0.565888] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMI [ 0.565937] bone-capemgr bone_capemgr.9: Skipping disabled cape with part# BB-BONELT-HDMIN [ 0.714324] bone-capemgr bone_capemgr.9: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G' [ 0.714439] bone-capemgr bone_capemgr.9: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI' [ 0.714540] bone-capemgr bone_capemgr.9: slot #6: 'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN' [ 0.714612] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-I2C1', version 'N/A', prio '0' [ 0.714653] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,BB-I2C1' [ 0.714725] bone-capemgr bone_capemgr.9: enabled_partno part_number 'BB-SPI1-SWP-01', version 'N/A', prio '0' [ 0.714762] bone-capemgr bone_capemgr.9: slot #8: 'Override Board Name,00A0,Override Manuf,BB-SPI1-SWP-01' [ 0.714928] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMI [ 0.714943] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMIN [ 0.715135] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715149] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.715228] bone-capemgr bone_capemgr.9: loader: before slot-7 BB-I2C1:00A0 (prio 0) [ 0.715240] bone-capemgr bone_capemgr.9: loader: check slot-7 BB-I2C1:00A0 (prio 0) [ 0.715732] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1) [ 0.718442] bone-capemgr bone_capemgr.9: loader: after slot-7 BB-I2C1:00A0 (prio 0) [ 0.718462] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'BB-I2C1-00A0.dtbo [ 0.718477] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'BB-I2C1-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 0.718506] bone-capemgr bone_capemgr.9: slot #7: dtbo 'BB-I2C1-00A0.dtbo' loaded; converting to live tree [ 0.720710] bone-capemgr bone_capemgr.9: loader: before slot-8 BB-SPI1-SWP-01:00A0 (prio 0) [ 0.720724] bone-capemgr bone_capemgr.9: loader: check slot-8 BB
[beagleboard] Re: Device tree overlays may load manually, but not at boot.
I found this: *...POSIX says that a non-interactive shell must not generate pathnames for a redirection; an interactive shell may do so, provided there is exactly one match.. * So although: echo BB-SPIDEV0/sys/devices/bone_capemgr.*/slots might work when you are doing it manually, you need to do something like this: #!/bin/sh -e slots=$(ls /sys/devices/bone_capemgr.*/slots) echo BB-SPIDEV0 $slots echo BB-SPIDEV1 $slots exit to make it run in a plain sh script -- 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.
