Booting issues on the ClearFog Pro.

This forum is for discussion about general software issues.

Booting issues on the ClearFog Pro.

Postby djsumdog » Thu Oct 06, 2016 9:50 pm

So I attempted to use the following instructions to load Arch on the ClearFog pro:

https://archlinuxarm.org/platforms/armv ... l/clearfog

Unfortunately, Arch did not boot. I did get Debian:Jessie running from the official image on the ClearFog (SolidRun) website. I'm not sure how to get to the console on this device. I don't have a JTAG/serial connector. I've found some blog posts that show the console output to minicom, but no one really explains how they get to it. Is the console accessible via just the microUSB port? When I plug it in I don't get a $this->bbcode_second_pass_code('', '/dev/ttyUSB*'). I tried loading my usbserial module on my Linux box with the product/vendor ID of this device that shows up when I plug in the ClearFog:

$this->bbcode_second_pass_code('', '
[177718.717421] usb 1-2: new full-speed USB device number 28 using xhci_hcd
[177718.888730] usb 1-2: New USB device found, idVendor=0403, idProduct=6015
[177718.888735] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[177718.888738] usb 1-2: Product: FT230X Basic UART
[177718.888741] usb 1-2: Manufacturer: FTDI
[177718.888743] usb 1-2: SerialNumber: DJ00H8I7
[178821.088029] usb 1-2: USB disconnect, device number 28
[178824.290288] usb 1-2: new full-speed USB device number 29 using xhci_hcd
[178824.461396] usb 1-2: New USB device found, idVendor=0403, idProduct=6015
[178824.461399] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[178824.461401] usb 1-2: Product: FT230X Basic UART
[178824.461402] usb 1-2: Manufacturer: FTDI
')

..but still no ttyUSB.

Anyway, the big issue. I can get Arch working. I load Debian:Jessie (solidrun's official port), keep /boot, /boot.scr and /boot.script, delete the rest, and then unpack the Arch zip (except for /boot obviously). Using the Jessie kernel and bootloader, I can boot arch.

I'd like to diagnose what's wrong with the Arch instructions/kernel. I went through that wiki line by line 2 or 3 times. I always install the bootloader in PCI/PCI mode. The only change I have to make is changing /sd/sd* to /dev/mmcblk* (my laptop's SD card reader shows sd cards as /dev/mmcblk*) and I use bash instead of sh on the uboot install script (sh causes an infinite loop; issue on the read command I think).

The other thing, I have an M.2 SSD I attached to this board. I copied the same setup (debian kernel + Arch base) to my M.2 and flipped the dip switches to boot from M2. It didn't work and I realized in the docks you need to use a different boot loader ... and de-solder a resistor (What the...?! Seriously? Come on!) and you still need the SD card for the environment variables anyway.

So instead, I thought maybe I can use the SDcard just for booting and have it mount my M.2 as root? When I boot to either Jessie or Arch, it can read/mount the M.2, so that should work? I tried modifying /boot.scr and /boot.script so root was /dev/sda1 instead of /dev/mmcblk0p1. That didn't work. Also, what is the difference between boot.scr and boot.script? One looks to be the boot.script with some binary/bootstrapping stuff at the top? If I run file, I get

$this->bbcode_second_pass_code('', 'boot.scr: u-boot legacy uImage, , Linux/ARM, Script File (Not compressed), 710 bytes, Tue Jul 5 22:42:57 2016, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0xF106DBC5, Data CRC: 0xF42DBC86')

..so it's u-boot with is vars attached after it? Do I edit boot.script and run something to generate boot.scr?

TL;DR:

    Can I get a console from my Linux box to the ClearFog Pro via microUSB (and if so how)?
    Are there any known issues with the current Wiki/Install docs and Arch kernel/uboot for this board? (Why does the Debian/Jessie kernel work but not the one in the arch instructions).
    Can I boot from SD and mount root (/) from my M.2 card?
djsumdog
 
Posts: 9
Joined: Tue Oct 04, 2016 8:22 pm

Re: Booting issues on the ClearFog Pro.

Postby moonman » Fri Oct 07, 2016 3:05 am

1. Clearfog has ttl to usb chip on board so you just need micro usb cable. Check your cable. I used a samsung one at dirst which was good for charging but did not work for data
2. Not that I know of. I will test install when i get time to make sure.
3. You can. Use uEnv.txt to change root device.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

Re: Booting issues on the ClearFog Pro.

Postby moonman » Fri Oct 07, 2016 6:21 am

Just reinstalled following all the instructions. Everything works.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

Re: Booting issues on the ClearFog Pro.

Postby djsumdog » Fri Oct 07, 2016 10:42 pm

Ah..I was missing ftdi_sio support in my Kernel. Added the module and I now have a ttyUSB0. :)

So I got a little further with console output:

$this->bbcode_second_pass_code('', '
minicom -o -D /dev/ttyUSB0


Welcome to minicom 2.6

OPTIONS: I18n
Compiled on Oct 2 2016, 16:40:27.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys


BootROM - 1.73

Booting from MMC


General initialization - Version: 1.0.0
Detected Device ID 6828
High speed PHY - Version: 2.0

Init Customer board board SerDes lanes topology details:
| Lane # | Speed| Type |
------------------------------|
| 0 | 3 | SATA0 |
| 1 | 0 | SGMII1 |
| 2 | 5 | PCIe1 |
| 3 | 5 | USB3 HOST1 |
| 4 | 5 | PCIe2 |
| 5 | 0 | SGMII2 |
-------------------------------
:** Link is Gen1, check the EP capability
PCIe, Idx 1: remains Gen1
PCIe, Idx 2: detected no link
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.39.0
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **


U-Boot 2013.01 (Jun 05 2016 - 07:56:34) Marvell version: 2015_T1.0p11

Board: A38x-Customer-Board-1
SoC: MV88F6828 Rev A0
running 2 CPUs
CPU: ARM Cortex A9 MPCore (Rev 1) LE
CPU 0
CPU @ 1600 [MHz]
L2 @ 800 [MHz]
TClock @ 250 [MHz]
DDR3 @ 800 [MHz]
DDR3 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM: 1 GiB
MMC: mv_sdh: 0
PCI-e 1 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 1.1
PCI-e 1: Detected No Link.
USB2.0 0: Host Mode
USB3.0 0: Host Mode
USB3.0 1: Host Mode

Map: Code: 0x3fecf000:0x3ff9738c
BSS: 0x3ffef15c
Stack: 0x3f9bef20
Heap: 0x3f9bf000:0x3fecf000
U-Boot Environment: 0x000f0000:0x00100000 (MMC)

Board configuration detected:
Net:
| port | Interface | PHY address |
|--------|-----------|--------------|
| egiga0 | RGMII | 0x00 |
| egiga1 | SGMII | In-Band |
| egiga2 | SGMII | In-Band |
egiga0 [PRIME], egiga1, egiga2
Hit any key to stop autoboot: 0
Checking for: /boot/uEnv.txt ...
** File not found /boot/uEnv.txt **
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Loaded environment from /boot/uEnv.txt
Checking if uenvcmd is set ...
Reset RTC...
Date: 1970-01-01 (Thursday) Time: 0:00:00
Reset RTC...
Date: 1970-01-01 (Thursday) Time: 0:00:00
** File not found /boot/zImage **
** File not found /boot/dtbs/armada-388-clearfog.dtb **
** File not found /boot/initramfs-linux.img **
Bad Linux ARM zImage magic!
Marvell>>
')
djsumdog
 
Posts: 9
Joined: Tue Oct 04, 2016 8:22 pm

Re: Booting issues on the ClearFog Pro.

Postby djsumdog » Sat Oct 08, 2016 12:19 am

I figured it out. I did not read step core carefully enough.

$this->bbcode_second_pass_code('', 'mkfs.ext4 -O ^metadata_csum,^64bit /dev/sdX1')

I got the < / >= flipped around when I was reading that. Now it boots up fine. :)
djsumdog
 
Posts: 9
Joined: Tue Oct 04, 2016 8:22 pm


Return to General

Who is online

Users browsing this forum: No registered users and 8 guests