Re: [beagleboard] Simultaneous boot, Windows and BBB - windows hangs
On Tuesday, June 3, 2014 5:47:52 PM UTC-4, William Hermans wrote: I've had PCs that would do this with regular USB HDD's attached at boot time. Or, more correctly this was a BIOS issue that would lock the PC up, if a USB storage device was attached at boot. The only thing that could fix this was if the USB device was selected as the primary boot device. Or removing the USB device at boot. I suspected the file-storage component of the driver because of this.. But the hang happens after the BIOS, at the Starting Windows screen while the four colors are flying towards you. On Tue, Jun 3, 2014 at 1:36 PM, Robert Nelson robert...@gmail.com javascript: wrote: Well, with no os running on the PC, how is the beagle suppost to request the power it needs over 'usb' to run? The fact windows locks up over that sounds like a usb host bug, try sup...@microsoft.com javascript: Yes it's definitely happening on the windows side. I'm not expecting a lot of help from them, but I should see what they say.. It also happens when I boot the bone first with its own power supply, and then boot windows after the bone boot process has started.. I don't think the beaglebone requests power over usb for this configuration. If I boot one, then the other, things are fine. In the latest Debian, how do I disable these gadgets individually? (Serial gadget, File storage gadget, RNDIS gadget?) /opt/scripts/boot/am335x_evm.sh line 76. Thanks! Bingo! If I comment this line out entirely windows boots okay sleep 15 right before that line works too. I tried changing options for the line, but the only ones that worked were ones that caused g_multi to not load. -- 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] Simultaneous boot, Windows and BBB - windows hangs
When I plug a Beaglebone black (Rev B or C) into some of the windows machines I have and power them both on simultaneously, windows (7) will freeze during the boot process. Has anybody else reported this? or experienced this? I haven't been able to find any help about this already published online. If I boot one, then the other, things are fine. I'm guessing it is one of the devices the Beaglebone exposes coming online during the beaglebone boot process. I'd like to disable them individually to see which one might be the culprit, but I can't figure out how they are started during the boot process. In the latest Debian, how do I disable these gadgets individually? (Serial gadget, File storage gadget, RNDIS gadget?) 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] Re: Dude, where's my BeagleBone Black?
C Wong, quick side answer.. check out machinekit! https://groups.google.com/forum/#!forum/machinekit -- 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: CLKOUT2 access in RCN 3.12 kernel?
I set my issue aside for a while (the 3.2 kernel is working okay for me now..) However, I did come across this link that discusses what changed in beaglebone device trees from 3.8 to 3.12. I figured it might be interesting reading for others as well. http://www.thing-printer.com/converting-device-tree-overlays-kernel-3-12/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: CLKOUT2 access in RCN 3.12 kernel?
I'm guessing that this is arch/arm/boot/dts/am335x-evm.dts. In 3.8 there is no mention of clkout2, the pinmux grabs lcd_pins_s0 In 3.12 in a similar-looking section, lcd_pins_s0 is replaced by clkout2_pin -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CLKOUT2 access in RCN 3.12 kernel?
Thanks for responding..
I did
grep clkout2 *.dts
in both directories and found that clkout2 didn't show up in the 3.8 but
did show up in 3.12
in 3.12 it shows up in am335x-evm.dts and also am335x-evmsk.dts.. (and
dove-cubox.dts but I don't think that is related)
I also just noticed that it also shows up in am335x-bone-common.dtsi,
(3.12) which now seems more likely to be the beaglebone related file.
Here's that chunk from my device tree file..
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
gpmc_pins: pinmux_gpmc_pins {
pinctrl-single,pins =
/* 0x20 = Fast, RX_enabled, pullup, pullup_enable, mode
0 */
0x000 0x20/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
PULLUP */
0x004 0x20/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
PULLUP */
0x008 0x20/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
PULLUP */
0x00C 0x20/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
PULLUP */
0x010 0x20/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
PULLUP */
0x014 0x20/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
PULLUP */
0x018 0x20/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
PULLUP */
0x01C 0x20/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
PULLUP */
0x020 0x20/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
PULLUP */
0x024 0x20/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
PULLUP */
0x028 0x20/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT |
PULLUP */
0x02C 0x20/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT |
PULLUP */
0x030 0x20/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT |
PULLUP */
0x034 0x20/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT |
PULLUP */
0x038 0x20/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT |
PULLUP */
0x03C 0x20/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT |
PULLUP */
0x078 0x04/* gpmc_ben1.gpmc_dir MODE4 | OUTPUT */
0x080 0x00/* gpmc_cscn1.gpmc_cscn1 MODE0 | OUTPUT */
0x08C 0x00/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
0x090 0x00/* gpmc_advn_ale.gpmc_advn_ale MODE0 |
OUTPUT */
0x094 0x00/* gpmc_oen_ren.gpmc_oen_ren MODE0 |
OUTPUT */
0x098 0x00/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
0x09C 0x00/* gpmc_ben0_cle.gpmc_ben0_cle MODE0 |
OUTPUT */
0x1b4 0x03/* xdma_event_intr1.clkout2 MODE3 |
OUTPUT */
;
};
};
};
I used BB-BONE-CAM3 as a starting point but yes, I'm mostly guessing at
what this stuff means.
My next guess is that the last line above is in the wrong section.. clkout2
is not a gpmc pin.
I don't have any /include/ lines in my file.. just
compatible = ti,beaglebone, ti,beaglebone-black;
from the CAM3 file I modified.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] CLKOUT2 access in RCN 3.12 kernel?
I've been successfully using the Arago 3.2.0 kernel in a Beaglebone (white) project that uses GPMC. I'd like to move to a more recent kernel, thinking that there are realtime fixes in 3.8+ that might help realtime performance. I've been able to stop using omap_mux and move to device tree. My code runs on 3.8 kernel for a little while, but then I get an oops that locks up everything. (but that's a topic for a different thread..) So, (thinking that's a kernel bug that may have been fixed in a more recent kernel,) I'm trying 3.12 instead. I'm able to get an SD card updated to 3.12 with wget http://rcn-ee.net/deb/saucy-armhf/v3.12.6-bone11/install-me.sh sudo bash ./install-me.sh and can compile my device tree file for it, but when I run my device tree file I get [ 110.746390] pinctrl-single 44e10800.pinmux: pin 44e109b4.0 already requested by ; cannot claim for 5000.gpmc [ 110.758839] pinctrl-single 44e10800.pinmux: pin-109 (5000.gpmc) status -22 [ 110.766597] pinctrl-single 44e10800.pinmux: could not request pin 109 (44e109b4.0) from group pinmux_gpmc_pins on device pinctrl-single [ 110.779699] omap-gpmc 5000.gpmc: Error applying setting, reverse things back -- which, as near as I can decipher, is telling me that something else (44e10800.pinmux, apparently) has grabbed clkout2 and won't let me use it. I'm just not sure how to find this culprit and make it give me my pin back. Any suggestions? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
