[samy03]

Hi Erik,

I figured it out. In reset supervision circuit SN74LVC1G06DCK got populated instead of SN74LVC1G07DCK, which was holding reset signal low. I just replaced the buffer from an older board and got it working.

Thank you

[samy03]

Neeraj,

I was finally able to get my network up and running. It turns out MDIO pin on LAN8710 was not making a good connection on my board, and I just re-soldered it and it worked. I really appreciate you and everyone at Octavo systems for helping me out with this.

Thanks,

Samy

[samy03]

Neeraj,

I have attached boot log for my custom linux image that I created using buildroot.

Samy

Attachments:

1. custom_linux_boot_log.txt

[samy03]

Neeraj,

I am using LAN8710 as my PHY and beaglebone also uses this PHY so I would assume it should work without making any change to this section of device tree. I have very little understanding of device tree. Can you please also explain what this line means:

phy_id = <&davinci_mdio>, <0>;

Is this supposed to look at PHYAD0?

[samy03]

Hi Neeraj,

I was able to get rid of this error by generating a custom U-boot and Kernel without USB support. But once I created custom U-boot, somehow patch for booting custom board got removed, so I had to program my EEPROM with magic number so I can run my custom U-boot.

Now I am having trouble with my PHY. I am not able to get my network up. At u-boot I get this error:

Could not get PHY for cpsw: addr 0

And at my kernel boot I get “PHY not found” error.

How can I fix this issue?

 

Thank you,

Samy

[samy03]

Hi Neeraj,

I tried booting up with beaglebone black image but it gets stuck at Uboot with following error:

starting USB…

USB0:   Port not available.

using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

MAC 98:84:e3:ae:08:53

HOST MAC de:ad:be:af:00:00

RNDIS ready

The remote end did not respond in time.missing environment variable: pxeuuid

Retrieving file: pxelinux.cfg/01-98-84-e3-ae-<wbr />08-53

using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

MAC 98:84:e3:ae:08:53

HOST MAC de:ad:be:af:00:00

RNDIS ready

I also tried building custom image and still get the same error. I am not sure if this error is coming from device tree or u-boot. I would really appreciate if you can help me with this error.

Thank you,

Samy

• This reply was modified 6 years, 9 months ago by samy03.

[samy03]

Sorry my bad. I was trying to execute make from my ubuntu machine, instead of running it from my RED board.

I got it working once I ran make on RED board.

[samy03]

Hi Eshtaartha,

 

I know this is an old post, but I lost my linux computer and had to get a new one. Now I am building device tree again and following the procedure in App note but I get the following error after executing make : “/bin/sh: 1: /usr/bin/dtc: Exec format error”

I would really appreciate your help.

Thank you

 

[samy03]

Hi Erik,

Thanks for your response. Just want to make sure, is this something that I can use: https://www.digikey.com/product-detail/en/panasonic-electronic-components/RP-SEMC08DA1/P122048-ND/6964963

Its a 8Gb eMMC with 153 FBGA package.

Thank you

[Author]

Posts