25 25
gprovost

Helios4 Support

Recommended Posts

@helios4noob Your issue is unrelated to Helios4 hardware. It's a software setup issue, could be on your computer / laptop trying to access the share drives on Helios4. You will find better help effectively on the OMV forum for that.

 

Have you tried to disable the firewall on you computer / laptop just to test if you can access the share drives without ? I  assume you are using windows machine.

 

As for the Helios4 froze that happened once, next occurrence check status of  LED8 and LED1 and let us know. (ref to this wiki page to identify LED : https://wiki.kobol.io/led/)

 

 

Share this post


Link to post
Share on other sites

I've had a running Helios4 system for almost a year, and it suddenly stopped working (there could have been a power outage, I don't know). When booted, the led next to the power inlet blinks slowly green, but it won't connect to the wired network, and it won't show me a login prompt over the serial connection.

 

- can I review the boot screen/tty from serial, without logging (boot process)?

- Shall I try to use the reset button on the board?

- Where should I check for logs on the SD card?

- Is there a way to boot from another medium (I know about the jumpers, but how to configure the medium when it's not booting at the moment)?

Share this post


Link to post
Share on other sites
(edited)
16 hours ago, Iskren Chernev said:

I've had a running Helios4 system for almost a year, and it suddenly stopped working (there could have been a power outage, I don't know). When booted, the led next to the power inlet blinks slowly green, but it won't connect to the wired network, and it won't show me a login prompt over the serial connection.

 

- can I review the boot screen/tty from serial, without logging (boot process)?

- Shall I try to use the reset button on the board?

Hi,

yes, you can see the boot process from serial. you can follow the instruction in our wiki. After the serial terminal ready, you can press the reset button to see the boot process since very beginning.

You should see something like:

U-Boot SPL 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800)
High speed PHY - Version: 2.0
Detected Device ID 6828
board SerDes lanes topology details:
 | Lane #  | Speed |  Type       |
 --------------------------------
 |   0    |  6   |  SATA0	|
 |   1    |  5   |  USB3 HOST0	|
 |   2    |  6   |  SATA1	|
 |   3    |  6   |  SATA3	|
 |   4    |  6   |  SATA2	|
 |   5    |  5   |  USB3 HOST1	|
 --------------------------------
High speed PHY - Ended Successfully
mv_ddr: mv_ddr-armada-17.10.4 
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR Training Sequence - Start scrubbing
DDR3 Training Sequence - End scrubbing
mv_ddr: completed successfully
Trying to boot from MMC1


U-Boot 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800)

SoC:   MV88F6828-A0 at 1600 MHz
DRAM:  2 GiB (800 MHz, 32-bit, ECC enabled)
MMC:   mv_sdh: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Model: Helios4
Board: Helios4
SCSI:  MVEBU SATA INIT
Target spinup took 0 ms.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs 

Net:   
Warning: ethernet@70000 (eth1) using random MAC address - 52:fc:90:b3:be:70
eth1: ethernet@70000
Hit any key to stop autoboot:  3  2  1  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
1979 bytes read in 104 ms (18.6 KiB/s)
## Executing script at 03000000
Boot script loaded from mmc
220 bytes read in 86 ms (2 KiB/s)
19717 bytes read in 353 ms (53.7 KiB/s)
4714605 bytes read in 852 ms (5.3 MiB/s)
5460016 bytes read in 1037 ms (5 MiB/s)
## Loading init Ramdisk from Legacy Image at 02880000 ...
   Image Name:   uInitrd
   Created:      2019-02-07  11:42:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4714541 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02040000
   Booting using the fdt blob at 0x2040000
   Using Device Tree in place at 02040000, end 02047d04

Starting kernel ...

But i think you won't see that screen.

LED8 near power inlet indicate the input voltage, if it's blink (nothing fancy here, just LED connected to 12V  3.3V) then it's a hardware problem. most probably the power adapter.

 

Do you have a voltmeter? Could you measure the voltage on these pin

839584136_male4pin.jpg.96ab051398e49235d1ddbcab0a9f76c7.jpg

 

to determine whether it's power adapter or on-board regulator failure.

Edited by aprayoga

Share this post


Link to post
Share on other sites

I measured the voltage (and shorted it for a few seconds while trying to do so, these pins are kinda hard to reach with other sticking pins :)), and it was 2.57 volts. I believe it should be 12V (unless its like the old apple chargers which switch a few seconds later). Shall I find a new power supply?

Share this post


Link to post
Share on other sites

Hi @gprovost,

 

Reading the wiki while waiting for the Batch3 , I was wondering if it would be possible to boot directly to a sata disk...

SPI-NOR Flash wiki page only mentions booting to a microSD card or USB drives. Would something like the following work ?

ext4load sata 0:1

Or does the concurrent access issue between SPI NOR Flash and SATA drives currently prevents this ? Thanks.

Share this post


Link to post
Share on other sites
27 minutes ago, MarcC said:

Hi @gprovost,

 

Reading the wiki while waiting for the Batch3 , I was wondering if it would be possible to boot directly to a sata disk...

SPI-NOR Flash wiki page only mentions booting to a microSD card or USB drives. Would something like the following work ?


ext4load sata 0:1

Or does the concurrent access issue between SPI NOR Flash and SATA drives currently prevents this ? Thanks.

 

Yes, you can boot from SATA disk but currently limited only from SATA1 port.

Take a look on following log:

U-Boot SPL 2018.11-00008-g8f200a3d28 (Jul 03 2019 - 08:01:15 +0800)
High speed PHY - Version: 2.0
Detected Device ID 6828
board SerDes lanes topology details:
 | Lane #  | Speed |  Type       |
 --------------------------------
 |   0    |  6   |  SATA0       |
 |   1    |  5   |  USB3 HOST0  |
 |   2    |  6   |  SATA1       |
 |   3    |  6   |  SATA3       |
 |   4    |  6   |  SATA2       |
 |   5    |  5   |  USB3 HOST1  |
 --------------------------------
High speed PHY - Ended Successfully
mv_ddr: mv_ddr-armada-17.10.4
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR Training Sequence - Start scrubbing
DDR3 Training Sequence - End scrubbing
mv_ddr: completed successfully
Trying to boot from SPI


U-Boot 2018.11-00008-g8f200a3d28 (Jul 03 2019 - 08:01:15 +0800)

SoC:   MV88F6828-A0 at 1600 MHz
DRAM:  2 GiB (800 MHz, 32-bit, ECC enabled)
MMC:   mv_sdh: 0
Loading Environment from SPI Flash... SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB
OK
Model: Helios4
Board: Helios4
SCSI:  MVEBU SATA INIT
Target spinup took 0 ms.
Target spinup took 0 ms.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs

Net:
Warning: ethernet@70000 (eth1) using random MAC address - ee:e0:5b:09:22:72
eth1: ethernet@70000
Hit any key to stop autoboot:  0
starting USB...
USB0:   MVEBU XHCI INIT controller @ 0xf10f4000
Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1:   MVEBU XHCI INIT controller @ 0xf10fc000
Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: device type unknown
... is now current device
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00
            Type: Hard Disk
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
  Device 0: (0:1) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00
            Type: Hard Disk
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
  Device 0: (1:0) Vendor: ATA Prod.: STEC MACH8 SSD Rev: 1031
            Type: Hard Disk
            Capacity: 57241.8 MB = 55.9 GB (117231408 x 512)
  Device 0: (1:1) Vendor: ATA Prod.: STEC MACH8 SSD Rev: 1031
            Type: Hard Disk
            Capacity: 57241.8 MB = 55.9 GB (117231408 x 512)
Found 4 device(s).

Device 0: (0:0) Vendor: ATA Prod.: TOSHIBA MK5065GS Rev: GJ00
            Type: Hard Disk
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
... is now current device
Scanning scsi 0:1...
Found U-Boot script /boot/boot.scr
2948 bytes read in 88 ms (32.2 KiB/s)
## Executing script at 03000000
Boot script loaded from scsi
199 bytes read in 54 ms (2.9 KiB/s)
18933 bytes read in 167 ms (110.4 KiB/s)
5408781 bytes read in 223 ms (23.1 MiB/s)
5590368 bytes read in 218 ms (24.5 MiB/s)
## Loading init Ramdisk from Legacy Image at 02880000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5408717 Bytes = 5.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02040000
   Booting using the fdt blob at 0x2040000
   Loading Ramdisk to 0fad7000, end 0ffff7cd ... OK
   reserving fdt memory region: addr=2040000 size=6a000
   Loading Device Tree to 0fa6a000, end 0fad6fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Helios4 boot from SPI with rootfs located on scsi 0:1

 

To access the SATA disk, you have to use scsi command instead of sata command

Share this post


Link to post
Share on other sites
16 hours ago, aprayoga said:

Yes, you can boot from SATA disk but currently limited only from SATA1 port.

Take a look on following log:

[...]

Helios4 boot from SPI with rootfs located on scsi 0:1

To access the SATA disk, you have to use scsi command instead of sata command

 

Thanks @aprayoga, this is great news.

 

As an alternative, is it also possible to write directly U-Boot to the SATA1 disk (the process should be similar to the microSD card process described in Wiki) and boot it directly by setting the SW1 dipswitch to SATA1 value ?

Share this post


Link to post
Share on other sites

@MarcC it is possible to write U-Boot directly to SATA disk but currently no U-Boot image for SATA available. and AFAIK,  the procedure a bit different but more similar like PC.  Write U-Boot SPL to disk boot sector then put u-boot.bin into FAT formatted 1st partition.

We are still experimenting with this, can not say when it would be ready.

 

Share this post


Link to post
Share on other sites
17 hours ago, Koen said:

Any ETA on Debian 10 (Duster) ?

 

Armbian Buster is ready, but we are still working at upgrading Linux Kernel and U-boot for Default and Next Armbian branch. Making the upcoming release a major Armbian release For Helios4. New OS images and Debian packages should be published in one to 2 weeks time max.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
25 25