I have just ported Linux kernel 3.17.3 to our board. This stops the system
going into OTG probing when the g_ether module is loaded. It still does a
single OTG probe when initially loaded but there is no every 2 seconds
probe.
If this fixes things for all USB modules, I don't know and I don't
On Thursday, November 20, 2014 8:35:49 AM UTC-5, terry.b...@googlemail.com
wrote:
Ok, I have now got somewhere with this. What seems to be happening at
least on our custom design (similar to BBB) is:
1. We have an oscilloscope on the USB0 VBUS line.
2. We have set the USB0
Just a quick google search, but the automatic reboot portion of the
second answer got my attention.
http://stackoverflow.com/questions/20467010/usb0-changed-the-mode-due-to-emi-using-am1808
Also for what it is worth, I've booted my BBB via external / self powered
USB
Hard drive in the past, and
Ok, I have now got somewhere with this. What seems to be happening at least
on our custom design (similar to BBB) is:
1. We have an oscilloscope on the USB0 VBUS line.
2. We have set the USB0 controller's mode to peripheral using the
DTB's dr_mode setting.
3. When the g_ether
We have been having a similar problem with an AM335x design using the
TPS65217 connected like a Beaglebone black.
We are using the 3.12.10 kernel and saw system resets every 14 hours or so.
We had set the USB ports to be host and peripheral types (in the boards
DTB) , however we still saw, on an
Just an FYI...
We are currently working on a project using Rev C BBB and RCN
3.13.11-bone12 kernel. We had been experiencing random reboots. Sometimes
multiple times per day and sometimes once per day, mostly at night. We
determined that the reboots were only occuring when the BBB was being
On Wed, Nov 19, 2014 at 3:57 PM, Rick Reynolds rwrma...@gmail.com wrote:
Just an FYI...
We are currently working on a project using Rev C BBB and RCN 3.13.11-bone12
kernel. We had been experiencing random reboots. Sometimes multiple times
per day and sometimes once per day, mostly at night.
The problem still isn't fixed on my end, but I've certainly been getting
closer.
I've tried
- Disabling all watchdog timers in u-boot and Linux, still crashes
- A different 5V power supply, still crashes
- Disconnecting all USB devices, still crashes
And to ensure I don't have faulty
On Saturday, November 8, 2014 10:01:52 AM UTC-5, Ives van der Flaas wrote:
However, not enoug of a difference apparently. I just had a sudden reset
occur. This is on a 3.18-rc2-bone1 with both a Dymo labelwriter and a
smartcard reader attached through USB.
Jens Peter Schroer gave me the
Setting the usb0 dr_mode to peripheral and disabling OTG in the .config
definitely makes a big difference. I have a 3.18-rc2-bone1 currently
running for almost 24 hours with this patch, much more than I've ever
previously achieved with 3.18 or 3.17.
Op woensdag 5 november 2014 01:36:09 UTC+1
However, not enoug of a difference apparently. I just had a sudden reset
occur. This is on a 3.18-rc2-bone1 with both a Dymo labelwriter and a
smartcard reader attached through USB.
The boot log after reset can be found at http://pastebin.com/YGnNpJyQ
Op zaterdag 8 november 2014 10:37:51
@David, did you try it on 3.17 or 3.18? Jens did his patch on 3.17 so there
could potentially be a difference there (unlikely that it is).
Op donderdag 6 november 2014 23:31:43 UTC+1 schreef david turvene:
On Thursday, November 6, 2014 11:10:37 AM UTC-5, Jens Peter Schroer wrote:
I have
I followed up on the USB OTG hint as mentioned in my previous post. I
patched the dtb for the bbb so that the mini usb port runs as peripheral
and not as OTG. The patch was deployed to 7 systems so far and they all are
stable (no reboot) since then on any of the systems. The uptime is more
I have followed the USB OTG hint as mentioned in my previous post. I
patched the dtb for the bbb so that the mini usb port runs as peripheral
and not as OTG. The patch was deployed to 7 systems so far and they all are
stable (no reboot) since then on any of the systems. The uptime is more
than 3
*If interested, I can post more details.*
Please do Jens, I am sure someone will find the information useful. Did you
by chance debug / bug report to the maintainer ?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
On Thursday, November 6, 2014 11:10:37 AM UTC-5, Jens Peter Schroer wrote:
I have followed the USB OTG hint as mentioned in my previous post. I
patched the dtb for the bbb so that the mini usb port runs as peripheral
and not as OTG. The patch was deployed to 7 systems so far and they all are
On Tuesday, November 4, 2014 9:01:53 AM UTC-5, Ives van der Flaas wrote:
Have you had *any* resets since the upgrade to the new u-boot version?
I've also been suspecting u-boot, hence my Meaning that I'm also running
an old u-boot. in the last post.
Yes, it has rebooted a couple times
Have you had *any* resets since the upgrade to the new u-boot version? I've
also been suspecting u-boot, hence my Meaning that I'm also running an old
u-boot. in the last post.
Op dinsdag 4 november 2014 00:18:43 UTC+1 schreef david turvene:
On Saturday, November 1, 2014 3:24:33 PM UTC-4,
On Saturday, November 1, 2014 3:24:33 PM UTC-4, david turvene wrote:
The system runs fine when I'm not messing around with the plugs, changing
the wifi properties, or sniffing. When I do any of these the system
occasionally silently reboots - I've been able to test up to 20 sniffing
On Friday, October 31, 2014 2:20:29 PM UTC-4, Ives van der Flaas wrote:
I can confirm that the problem still exists on the 3.18-rc2-bone1.
Running the RCN 3.18-rc2-bone1 my system has rebooted several times over
the weekend (EST). This is not good for me - and I've been trying to
figure
I just had another reboot on 3.18-rc2-bone1
On Friday, October 31, 2014 9:06:33 AM UTC+1, Ives van der Flaas wrote:
I'm currently trying the 3.18-rc2-bone1, no issues so far. I won't be able
to check on them during the weekend so I'll know by monday.
Op donderdag 30 oktober 2014 17:36:34
I can confirm that the problem still exists on the 3.18-rc2-bone1.
--
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
Op donderdag 30 oktober 2014 18:15:33 UTC+1 schreef William Hermans:
So I'm curious. Did all of you follow Roberts DebianOnARM kernel build
instructions, or are you all using a prebuilt image ?
I'm using a pretty old prebuilt 13.04 image (with lots of libraries and
scripts with quite a few
Hi Ives,
I am experiencing the same issue with our beaglebones (several of them). We
are using Robert C Nelson's latest 3.17.1-bone4 kernel image, and after
some time they reboot. Beside that the kernel is much more stable than any
other I have tried.
The only clue I have come across was in
On Thursday, October 30, 2014 5:50:43 AM UTC-4, Ives van der Flaas wrote:
I'm running Robert C Nelson's latest 3.17 kernel (3.17.1-bone4) because I
need the new TI musb babble recovery code. It seems however that I'm having
some strange instability on my BBB. After somewhere between 10 and
On Thu, Oct 30, 2014 at 11:34 AM, david turvene dturv...@gmail.com wrote:
On Thursday, October 30, 2014 5:50:43 AM UTC-4, Ives van der Flaas wrote:
I'm running Robert C Nelson's latest 3.17 kernel (3.17.1-bone4) because I
need the new TI musb babble recovery code. It seems however that I'm
Are you guys still seeing this with 3.18-rc2?
if you have my repo in /etc/apt/sources.list
sudo apt-get update
sudo apt-get install linux-image-3.18.0-rc2-bone1
sudo reboot
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
@Robert - I just upgraded to your image and it
27 matches
Mail list logo
