I have a BBB with Ubuntu 14.04 (Linux arm 3.8.13-bone56) and their repo
version of owserver (2.8p15-1ubuntu4 armhf). With a strong enough passive
pullup (<1K) I can read temperatures from my DS18B20, via w1 and BBB GPIO
45. (If the pullup is not strong enough, the temperatures from the 1-Wire
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robert...@gmail.com
javascript: wrote:
We assume phy_mask to be 100% correct. Maybe we should just force
the dt value of phy_id always into phy_mask?
I really need to find a board that 'never' boots with 0xfffe..
Back when I had
On Tuesday, November 25, 2014 5:11:56 AM UTC-8, Gerald wrote:
means the SD card is unreadable as a boot source and it cannot read
the eMMC either. It is looking for a boot source.
So you are saying that even though it was previously booted from the uSD,
and was not power cycled, it
My Rev.A6 BBB had been running solidly 24/7 for months, with only
explainable software-related crashes. But in the last week it has just hung
twice, with no relation to software functions, nothing unusual in the logs,
and D2/3/4 on solid.
It is powered by an analog regulator from my solar
On Wednesday, July 23, 2014 3:54:00 PM UTC-7, cmid...@gmail.com wrote:
The davinci mdio driver should report a phymask and that value is used to
update the device tree.
Back when I had this problem I tried hard to find out where the phymask
comes from, and never succeeded. At that time
Gerald said:
The issue is that the processors interferes with the default address
settings when the PHY reads the pins. If the SW looks for the other
addresses, it works fine.
Could we get a clue about which addresses are the problem?
Maybe the addresses 4a10 vs. 4a101000?
davinci_mdio
Got it! (Chrome print to PDF, copy from the print...)
-
3.7.1 PHYAD[2:0]: PHY Address Configuration
The PHYAD[2:0] configuration straps are driven high or low to give each PHY
a unique address. This address is latched into an internal register at the
end of a hardware reset (default =
In my intended application, my BBB absolutely must default to booting from
the uSD when power is applied. I know I could short the boot switch, or
move pull-up/down resistors, or create a hardware switch gated from reset,
but I don't want to lose hardware compatibility with other BBB boards, or
My long but successful learning experience is reported in:
https://groups.google.com/forum/#!topic/beagleboard/zNtdwtPf2Q8
Definitely not simple, but possible... Without making any changes to the
eMMC installation!
On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote:
Robert
and Windows disagree about the usb0 MAC, when they agree
about the eth0 MAC?
On Tuesday, January 21, 2014 3:01:18 PM UTC-8, Loren Amelang wrote:
My board is back from RMA, with what looks like a new ethernet chip. It is
ever so slightly raised up along one edge, though the pin alignment
Guess this issue is solved, but this seems like the best place for my
comment.
I always see davinci_mdio 4a101000.mdio: detected phy mask fffe,
never fffb, so that may be the critical part of your error.
But I also always see
-
libphy: PHY 4a101000.mdio:01 not found
net eth0: phy
My board is back from RMA, with what looks like a new ethernet chip. It is
ever so slightly raised up along one edge, though the pin alignment and
soldering job are perfect. I guess it could have been that way before, but
usually that's a sign of manual replacement. The only info I was able to
@Victor:
In your first post, you had exactly my error report. So do I understand
correctly you tried the two older images listed below and received the
totally different error reports? I've never seen any of those messages, but
I've only tried newer images, like
Trying to understand this... It seems you are saying the default state of
the TPS65215C is to have the AC pin internally connected to the USB pin.
But the datasheet says:
-
AC input is prioritized over USB input, i.e. if both inputs are valid,
current is pulled from the AC input
RMA initiated. Hope they reveal what went wrong with my board!
Found one clue, my fears about importbootenv are probably unfounded:
http://lists.busybox.net/pipermail/buildroot/2013-September/078135.html
---
On Thu, 12 Sep 2013 18:41:43 -0500, Ryan Barnett wrote:
Some boards in u-boot support
I see the TPS2051 in the USB Host section of the schematic, but it is fed
from SYS_5V. Isn't that _after_ the TPS65217C shuts everything off when the
input voltage exceeds an average of 6V?
I guess if you're being absolutely proper, the 2051 says 6.0V absolute max
and the 65217 says it limits
, RobertCNelson wrote:
On Mon, Jan 6, 2014 at 12:33 AM, Loren Amelang lorena...@gmail.com
wrote:
@RobertCNelson: Your kernel is out of date, please upgrade to
v3.8.13-bone35 first...
That kernel version is from attempts to boot Ubuntu. Maybe I could find
a
newer Ubuntu image,
http
, Jan 6, 2014 at 12:33 AM, Loren Amelang
lorena...@gmail.comjavascript:
wrote:
@RobertCNelson: Your kernel is out of date, please upgrade to
v3.8.13-bone35 first...
That kernel version is from attempts to boot Ubuntu. Maybe I could find
a
newer Ubuntu image,
http://elinux.org
Robert,
Sorry! Me again...
I have your Saucy image. Verified. But it appears it requires your
setup_sdcard script to be run, from a Linux machine. I've been using
Win32DiskImager... So I've copied it to the netbook, and I see the script,
but when I plug in my uSD card it says my
Vaibhav,
I've now been through six different images and they all end up with the
same panic. I don't know what else to do except push on the RMA people for
a hardware change. But then I'd be afraid I'd create the same problem on a
new board...
As for command timing, I've seen vastly
loadaddr=0x8020
Help! I need some better suggestions than to try yet another image.
Loren
On Monday, January 6, 2014 3:30:43 PM UTC-8, RobertCNelson wrote:
On Jan 6, 2014 5:27 PM, Loren Amelang lorena...@gmail.com javascript:
wrote:
Robert,
Sorry! Me again...
I have your
@RobertCNelson: Your kernel is out of date, please upgrade to
v3.8.13-bone35 first...
That kernel version is from attempts to boot Ubuntu. Maybe I could find a
newer Ubuntu image, but I have the same kernel panic problem trying to boot
Angstrom. It only says:
## Booting kernel from Legacy
@Vaibhav,
Just found this:
http://web.archiveorange.com/archive/v/vEQ2y6LmBVoCWJwTbcnr
about a problem with clocks not being enabled before mdio: probe - which
seems directly applicable to my Ubuntu fail!
Make the driver control the device clocks. Appearantly, the Davinci
platform probes
23 matches
Mail list logo
