[mdframe]

Yes, the process of placing an active network on this board is more of a pandora’s box. What I actually found in the end is that I must connect the espressobin to my switch directly. My normal connection to my switch is through the wall plate but apparently the connection is very sensitive and once I connected to a switch it came right up with my interfaces settings.

Thank you for sharing your network so we can help others, here is what I found works in my environment to get all three ports active:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
#source-directory /etc/network/interfaces.d
auto eth0
iface eth0 inet manual

auto lo
iface lo inet loopback

auto wan
iface wan inet dhcp
pre-up /sbin/ifconfig eth0 up

auto lan0
iface lan0 inet dhcp
pre-up /sbin/ifconfig eth0 up

auto lan1
iface lan1 inet dhcp
pre-up /sbin/ifconfig eth0 up
~

Hopefully this information will help other to prevent the hours which turned into days working through the network setup.

Thanks,

Matt

[mdframe]

Mike,

Thanks for the tip. I have tried various combinations but still no luck. I am thinking the ethernet is very touchy with this board. Are you connecting directly into your switch? I am connecting to a wall jack which is wired to my switch and I read somewhere on this forum where another user was having the same issue with not getting the DHCP address and did not get it resolved until connecting directly to a switch. I don’t have a spare at the moment to try that solution.

When you get your system online if you could provide your interface details I would appreciate the information.

Thanks again,

Matt

[mdframe]

Thank you so much for providing this information. I had some of it correct however with the updated information you provided I am seeing the WAN port stop linking with no lights when booting and the following messages are displayed on boot:

[ OK ] Found device /sys/subsystem/net/devices/wan.
[ OK ] Found device /sys/subsystem/net/devices/lan1.
[ OK ] Found device /sys/subsystem/net/devices/eth0.
[FAILED] Failed to start Raise network interfaces.
See ‘systemctl status networking.service’ for details.
[ OK ] Reached target Network.
Starting Network Name Resolution…
Starting /etc/rc.local Compatibility…

I am using the right-most ethernet jack for connecting to my network. The middle and left most jacks still have lights when I move my ehternet cable but the right most seems to be off.

Any other suggestions?

Thank you very much for your support.

Matt

[mdframe]

Hi,

I am still a newbie with Linux and Ubuntu and I have tried what I thought was the solution here to get my espresso board on my network. Would you be so kind to state what specifically you do in the u-boot params and ubuntu files to get networking up? I appreciate the help very much.

Thank you,

Matt

[mdframe]

No it does not. You must use the 12v power supply. I recently proved this to myself. You will be unable to get into the basic console mode without the power supply and the instructions are incorrect for initial start, you will not get to boot into any type of operating system.

[mdframe]

I’m using this one from Amazon
Power Supply

[mdframe]

Slab,

Thanks for all the information, very informative. Quick question about your last statement, if you mucked around with it. Is that the process to reset it back to default or to set it for the new card created above?

Thanks,

Matt

[mdframe]

For awareness and I do not know why, but I was able to reproduce the > E > E situation on my Windows workstation with Putty then connected to my Ubuntu workstation with Kermit and it came back to the Marvevll>> command prompt. Now I am fighting with the situation where it locks up in the first minute with running ubuntu 16.04. I read somewhere about setting the governor command so will update once I find that and retry.

[mdframe]

I was able to get the board out of the > E > E sequence by booting and connecting from a Ubuntu workstation with Kermit. I was using Putty when I was getting the strange behavior. After booting with the Ubuntu workstation I can now use Putty again from Windows and get the Marvell>> command prompt.

[mdframe]

Thanks David, I found the same issue in the SD image topic however now the board is unresponsive. I appreciate your time and support on the challenges I am encountering.

Take care,

Matt

[mdframe]

Thanks to this support topic and group I was finally able to get my Ubuntu image to load and execute, however after about a minute the console locked up. I powered off as gracefully as possible with this board now I have the same issue @biothundernxt is reporting with > E, > E.

I am assuming the firmware is now corrupt and their is no way back. Any suggestions?!?!?!?!?

[mdframe]

Thanks David for confirming what I was experiencing. I went ahead and built a bootable Ubuntu micro-sd card however had no luck with that either. Both of my Linux boxes read and show information on the 16gb card correctly, which was built on Linux as a ext4 file system, however the Espresso only shows a directory structure with 0 bytes in all folders. I followed all the directions from this site and then performed it a second time just to make sure I didn’t miss anything however the ext4 Marvell command only shows empty folders. Do you have any hints on how to get the Espresso to read micro-sd’s maybe a smaller card or some other trick? I really want to give this card a fair shake with a project I am working.

Thanks again for the help.

Matt

[mdframe]

You definitely need the 12v adapter to get the console to work. Now that I have it the UBoot image is starting and reporting issues with the onboard image load. I have not added any USB or micro-sd cards to the device at this point. I was just trying to follow the “Getting Started” information prior to adding or performing any activities. If you look at the information below you will see the errors.

Booting Trusted Firmware
BL1: v1.2(release):armada-17.02.0:
BL1: Built : 17:28:05, May 18 2NOTICE: BL2: v1.2(release):armada-17.02.0:
NOTICE: BL2: Built : 17:28:06, May 18 20NOTICE: BL31: v1.2(release):armada-17.02.0:
NOTICE: BL31:

U-Boot 2015.01-armada-17.02.0-g48dc978 (May 18 2017 – 17:28:01)

I2C: ready
DRAM: 1 GiB
Board: DB-88F3720-ESPRESSOBin
CPU @ 1000 [MHz]
L2 @ 800 [MHz]
TClock @ 200 [MHz]
DDR @ 800 [MHz]
Comphy-0: PEX0 2.5 Gbps
Comphy-1: USB3 5 Gbps
Comphy-2: SATA0 5 Gbps
Now running in RAM – U-Boot at: 3ff2b000
U-Boot DT blob at : 000000003fa18168
MMC: XENON-SDHCI: 0
SF: Detected W25Q32DW with page size 256 Bytes, erase size 4 KiB, total 4 MiB
PCIE-0: Link down
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
Net: neta0
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
** Bad device mmc 0 **
Card did not respond to voltage select!
** Bad device mmc 0 **
Bad Linux ARM64 Image magic!
Marvell>>

Can the internal firmware image be reloaded?

[mdframe]

Thanks David, that all matches my attempts. I have tried connecting with two Windows machines and an Ubuntu with no luck. I do get a solid green light and the board is recognized by all connections I just never receive anything other than a blank screen.

I don’t believe it will startup on 5v so I have ordered a 12v power supply. I could only guess at the plug size since specs are not listed anywhere on this site. I will update my post once I get the new power supply.

[Author]

Posts