Hi, Adding to this discussion a bit, hope you are all still there now and then...
I had some stability issues with a WiFi dongle on the PocketBeagle. I am running it with a USB cape. It used to run stable on battery power with P1,1 and P1,7 connected with each other. Only problem I had, I did not see an ip address from my wifi dongle (connected to the standard micro USB connection). I really needed to have a fixed ip address and decided to accomplish that using connmanctl. After successfully changing the connmanctl settings though the connection wasn't stable anymore. Using the micro USB on the micro USB connection it would sometimes connect, stay on for a few ping's and then disconnect. Once it stayed up for a whole minute!!! Connecting it to a USB port on the cape it would drop out, come back up for a ping, drop out again for about 10 to 20 pings, etcetera. When using the micro-USB connected to the computer though and powering the cape with the (powered) USB-dongle in it, the connection stayed stable. Which suggests a power issue. While using battery power I did connect VIN, VBUS and VIN-USB to a 5V stepDown board (from a LiPo, two cells) the only power input I had not connected yet was Vbat. While connecting Vbat, it seemed my board fried (power blinks about once a second now, further no response). I have had these PIN's connected before so it seems unlikely that that is the reason. I probably made some other mistake. My system still comes up on another PocketBeagle. My questions / requests: 1. Could wiring P1,1; P1,5; P1,7 and Vbat together on a 5V input pose a problem? (probably better not to connect a micro USB cable to the computer at the same time) 2. Could the instability of the WiFi dongle connection be caused by not connecting Vbat? (I have not been able to test it since the board fried while doing that) 3. Any suggestions for checking my boards demise or a recipe for possibly reviving it would we welcome. Best, Hans. Op vrijdag 16 augustus 2019 15:18:10 UTC+2 schreef Graham Haddock: > > >>> Does anyone have any input as to why the PocketBeagle design fails and > >>> why the BBBW works ? > > Robert Nelson is really the right person to answer that. > > From what I understand, during boot, uBoot examines the configuration > EEPROM and decides which files/modules to load. Even though the hardware > is identical, it could load different modules, if the configuration > EEPROM is different. So, one load has the bug, the other doesn't. > > Or, you are actually running different revision levels of silicon, and > one has a bug. > > > >>> Also if Tying VIN_USB to VIN_AC works, would the problem go away if a > >>> battery was connected to VIN_BAT ? > > I have never tried that, but definitely worth a try. It is a third > separate isolated power input. I assume with different management software. > > > >>> Any thoughts would be appreciated. > Beagleboard.org needs to decide if this is a serious enough problem that it > is worthy of being fixed. So far, they have decided that we don't know > what > we are doing, and are inducing a spurious problem; or that it is not > serious > enough a problem to spend the time fixing. I personally think it prevents > the PocketBeagle from being used for any serious application. > > On Fri, Aug 16, 2019 at 12:35 AM Dave <m...@dlasys.net <javascript:>> > wrote: > >> As I have noted in a previous post, I am seeing this problem on a board >> with a design derived from the pocketBeagle. >> Based on the information here we have managed a workaround - tying >> VIN_USB to VIN_AC, and as a consequence have several boards that have been >> runing for over 48hours, when we could not reach 18hrs before and often had >> resets every 30min. >> >> I have run the same software with nearly the same devicetree and the same >> linux(5.1.18) on a BBBW without any failures. >> >> I have compared the schematic of the BBBW which also uses that OSD335X >> SOC with that of my board and the pocketBeagle and can not see a >> meaningful difference in the input power design. >> >> Does anyone have any input as to why the PcketBeagle design fails and why >> the BBBW works ? >> >> Also if Tying VIN_USB to VIN_AC works, would the problem go away if a >> battery was connected to VIN_BAT ? >> >> Any thoughts would be appreciated. >> >> Though atleast we have a workarround now. >> >> Thank you. >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> 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/FwmkeG4itT0/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> beagl...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/dadd11c2-3887-4c87-8d02-0048fd10dd92%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/dadd11c2-3887-4c87-8d02-0048fd10dd92%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/efa9496f-3f88-4a6c-abcf-9706168fff2c%40googlegroups.com.
