SSP No Longer Boots

I purchased an SSP new from Perfect Circuit a few days ago, and now it’s no longer able to get past the graphical splash screen, before any startup output from the kernel shows. This started when another module, Mordax DATA, froze up, so I restarted my entire chassis. I had a Keith McMillen QuNexus Red plugged into the right USB port, and I was using that successfully before the DATA froze. When the boot loop started, I thought that maybe it was trying to draw too much power, so I unplugged the QuNexus, but this didn’t help. I then unplugged every other module from power, which also didn’t help.

Things I’ve tried:

Nothing has helped, and the symptoms are the same. I’m using a new (purchased at the same time as the SSP, so a few days old) Intellijel 104HP Palette. All my other modules still work fine.

I’m fairly well experienced with embedded devices in both my professional and personal life, and I happened to have a Bus Pirate laying around to hook up to the serial debug header on the back of the SSP. After following instructions from LAN Port? , I was able to get the serial debug output, which doesn’t seem to be very revealing:

U-Boot SPL 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44)

U-Boot 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44 -0700)

Model: Firefly-RK3288

DRAM: 2 GiB

MMC: dwmmc@ff0c0000: 1

Using default environment

In: serial

Out: serial

Err: serial

Net: Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot: 0

gpio: pin 6 (gpio 6) value is 1

gpio: pin i8 (gpio 264) value is 1

gpio: pin i9 (gpio 265) value is 1

reading splash.bmp

769078 bytes read in 61 ms (12 MiB/s)

Retrieving file: /extlinux/extlinux.conf

reading /extlinux/extlinux.conf

248 bytes read in 8 ms (30.3 KiB/s)

1: kernel-4.4

Retrieving file: /zImage

reading /zImage

7142056 bytes read in 504 ms (13.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=d12ad4f6-2ae1-4071-b747-8807fd16e0dc rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

Retrieving file: /rk3288-percussa-engine-euro.dtb

reading /rk3288-percussa-engine-euro.dtb

43019 bytes read in 11 ms (3.7 MiB/s)

## Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000

Loading Device Tree to 0fff2000, end 0ffff80a … OK

Starting kernel …

U-Boot SPL 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44)

U-Boot 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44 -0700)

Model: Firefly-RK3288

DRAM: 2 GiB

MMC: dwmmc@ff0c0000: 1

Using default environment

In: serial

Out: serial

Err: serial

Net: Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot: 0

gpio: pin 6 (gpio 6) value is 1

gpio: pin i8 (gpio 264) value is 1

gpio: pin i9 (gpio 265) value is 1

reading splash.bmp

769078 bytes read in 61 ms (12 MiB/s)

Retrieving file: /extlinux/extlinux.conf

reading /extlinux/extlinux.conf

248 bytes read in 8 ms (30.3 KiB/s)

1: kernel-4.4

Retrieving file: /zImage

reading /zImage

7142056 bytes read in 504 ms (13.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=d12ad4f6-2ae1-4071-b747-8807fd16e0dc rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

Retrieving file: /rk3288-percussa-engine-euro.dtb

reading /rk3288-percussa-engine-euro.dtb

43019 bytes read in 11 ms (3.7 MiB/s)

## Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000

Loading Device Tree to 0fff2000, end 0ffff80a … OK

Starting kernel …

U-Boot SPL 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44)

U-Boot 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44 -0700)

Model: Firefly-RK3288

DRAM: 2 GiB

MMC: dwmmc@ff0c0000: 1

Using default environment

In: serial

Out: serial

Err: serial

Net: Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot: 0

gpio: pin 6 (gpio 6) value is 1

gpio: pin i8 (gpio 264) value is 1

gpio: pin i9 (gpio 265) value is 1

reading splash.bmp

769078 bytes read in 61 ms (12 MiB/s)

Retrieving file: /extlinux/extlinux.conf

reading /extlinux/extlinux.conf

248 bytes read in 8 ms (30.3 KiB/s)

1: kernel-4.4

Retrieving file: /zImage

reading /zImage

7142056 bytes read in 504 ms (13.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=d12ad4f6-2ae1-4071-b747-8807fd16e0dc rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

Retrieving file: /rk3288-percussa-engine-euro.dtb

reading /rk3288-percussa-engine-euro.dtb

43019 bytes read in 11 ms (3.7 MiB/s)

## Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000

Loading Device Tree to 0fff2000, end 0ffff80a … OK

Starting kernel …

U-Boot SPL 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44)

U-Boot 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44 -0700)

Model: Firefly-RK3288

DRAM: 2 GiB

MMC: dwmmc@ff0c0000: 1

Using default environment

In: serial

Out: serial

Err: serial

Net: Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot: 0

gpio: pin 6 (gpio 6) value is 1

gpio: pin i8 (gpio 264) value is 1

gpio: pin i9 (gpio 265) value is 1

reading splash.bmp

769078 bytes read in 61 ms (12 MiB/s)

Retrieving file: /extlinux/extlinux.conf

reading /extlinux/extlinux.conf

248 bytes read in 8 ms (30.3 KiB/s)

1: kernel-4.4

Retrieving file: /zImage

reading /zImage

7142056 bytes read in 504 ms (13.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=d12ad4f6-2ae1-4071-b747-8807fd16e0dc rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

Retrieving file: /rk3288-percussa-engine-euro.dtb

reading /rk3288-percussa-engine-euro.dtb

43019 bytes read in 11 ms (3.7 MiB/s)

## Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000

Loading Device Tree to 0fff2000, end 0ffff80a … OK

Starting kernel …

U-Boot SPL 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44)

U-Boot 2017.03-rc3-g6bb0631783 (Aug 26 2017 - 19:04:44 -0700)

Model: Firefly-RK3288

DRAM: 2 GiB

MMC: dwmmc@ff0c0000: 1

Using default environment

In: serial

Out: serial

Err: serial

Net: Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot: 0

gpio: pin 6 (gpio 6) value is 1

gpio: pin i8 (gpio 264) value is 1

gpio: pin i9 (gpio 265) value is 1

reading splash.bmp

769078 bytes read in 61 ms (12 MiB/s)

Retrieving file: /extlinux/extlinux.conf

reading /extlinux/extlinux.conf

248 bytes read in 7 ms (34.2 KiB/s)

1: kernel-4.4

Retrieving file: /zImage

reading /zImage

7142056 bytes read in 504 ms (13.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=d12ad4f6-2ae1-4071-b747-8807fd16e0dc rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

Retrieving file: /rk3288-percussa-engine-euro.dtb

reading /rk3288-percussa-engine-euro.dtb

43019 bytes read in 11 ms (3.7 MiB/s)

## Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000

Loading Device Tree to 0fff2000, end 0ffff80a … OK

Starting kernel …

Any additional ideas of what to try would be greatly appreciated. I have multimeters, a real oscilloscope, etc if any of that would be useful here. The one thing I don’t have is a different eurorack power board to try.

hmm, sounds like its not booting the loading rootfs and consequently synths.

thats a bit odd, since the sdcard image is all thats required for this (afaik), so assuming this image has been successfully written to the sdcard , this should be ‘as new’

what your log seems to show, is that the bootloader is loading the kernel, starting it, then appears to restart it again… perhaps either crashing? or its not seeing the rootfs?
( I don’t see any mention of the rootfs, or the main system processes starting)

unfortunately, you have done all that i can think of/would do…so can only re-iterate…

my suspicion would be a corrupted sdcard, either due to sdcard or down to how the image has been written… but you have retried these.

I guess, I would try to check the image on another linux computer (as you mention you have ubuntu to hand)… it should be able to mount the card and rootfs - and check it ‘looks ok’

if the sdcard is ok, Im not sure what’s going on…

note: i tried to boot my ssp without the sdcard to see if something is stored on the emmc, but when I do this I don’t get the splash screen… so this indicates that the splash is always read from the sdcard, so it is booting off your sdcard… so seems to read at least the first partition of sdcard.

my gut feeling (and its only that) is that for some reason the rootfs is not able to be mounted.
… so as above, that is what I would be looking for, in terms of it being written properly to the sdcard, and also be able to be mounted by another linux box.

(Id assume the download is fine, since I don’t think it would verify if it was corrupted?!)

perhaps its worth reaching out directly via : https://www.percussa.com/contact/

note: you don’t need latest SYNTHOR for this booting process, that comes much later… so id focus on the full sdcard image… once that works :crossed_fingers: you can look at the SYNTHOR binary update.

btw: as you are new to the SSP.

a power-cycle should not cause any issues or corruptions… that is odd in itself.

we don’t have any ‘shutdown’ procedure for the SSP, so all of us just by switch off the power…
so it doesn’t sound like what you did was in anyway ‘unusual’ … my SSP has therefore been power cycled countless times… and Ive never had an issue with it not rebooting, and I don’t think Ive seen reports of it here.

(of course, thats not to say sdcard can never fail, they do… but seems really unlucky on a brand new sdcard)

1 Like

Thanks much for your replies and all your work on the SSP @technobear !

OK, so I’ve tried a third SD card, a Sandisk Max Endurance 256GB v30 U3 SDXC with the Asus TinkerBoard Debian Stretch v2.2.9-20210624 image (I chose this because it’s another RK3288 board with ready-to-go images), and this is what I get from the serial interface:

UART>(3)
UART bridge
Reset to exit
Are you sure? y
DDR Version 1.08 20190523
In
Channel a: DDR3 533MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel b: DDR3 533MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Memory OK
Memory OK
OUT
Boot1 Release Time: Nov 27 2019 15:30:08, version: 2.58
ChipType = 0x8, 222
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=14910MB
FwPartOffset=2000 , 2000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=244016MB
FwPartOffset=2000 , 0
StorageInit ok = 44460
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part:  0, name:            uboot, start:0x4000, size:0x2000
GPT part:  1, name:            trust, start:0x6000, size:0x2000
GPT part:  2, name:             misc, start:0x8000, size:0x2000
GPT part:  3, name:             boot, start:0xa000, size:0x10000
GPT part: name:         recovery, start:0x1a000, size:0x10000
GPT part:  5, name:           backup, start:0x2a000, size:0x10000
GPT part:  6, name:         userdata, start:0x3a000, size:0x20000
GPT part:  7, name:           rootfs, start:0x5a000, size:0x67abf0
find part:uboot OK. first_lba:0x4000.
find part:trust OK. first_lba:0x6000.
LOADER Check OK! 0x4000, 210447
TOS    Check OK! 0x6000, 300337
Enter Trust OS
INF [0x0] TEE-CORE:init_primary_helper:385: Core0 Initializing (1.1.0-423-g6a30fc35 #10 Fri Mar 13 01:56:59 UTC 2020 arm)


INF [0x0] TEE-CORE:init_primary_helper:386: Release version: 1.3


INF [0x0] TEE-CORE:init_primary_helper:387: Next entry point address: 0x200000


INF [0x0] TEE-CORE:init_teecore:83: teecore inits done



U-Boot 2017.09 #leslie_yu (Jun 24 2021 - 14:02:54 +0000)

Model: Evb-RK3288
PreSerial: 2
DRAM:  2 GiB
Sysmem: init
Relocation Offset: 00000000, fdt: 7be1cc38
no mmc device at slot 1
Found IDB in SDcard
dwmmc@ff0c0000: 1 (SD), dwmmc@ff0f0000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: EFI
boot mode: None
Found DTB in boot part
DTB: rk-kernel.dtb
HASH(c): OK
Android header version 0

Additionally, I’ve tried flashing with Windows 10 and a different SD card adapter just to be sure. No change. I’m starting to think that the image may be bad. I tried with The Unarchiver on Mac as well with the same result again. Here are the MD5 sums and disk infos for the SD cards I’ve made using the official image I linked to above:

❯ md5 ssp-*
MD5 (ssp-sandisk-extremepro-32gb-230720191843 (1).zip) = d05c74422ab5dad4d1e6c4f5f72f15e6
MD5 (ssp-sandisk-extremepro-32gb-230720191843 (2).zip) = d05c74422ab5dad4d1e6c4f5f72f15e6
MD5 (ssp-sandisk-extremepro-32gb-230720191843 (3).zip) = d05c74422ab5dad4d1e6c4f5f72f15e6
MD5 (ssp-sandisk-extremepro-32gb-230720191843.zip) = d05c74422ab5dad4d1e6c4f5f72f15e6
❯ md5 ssp/ssp-sandisk-extremepro-32gb-230720191843.img
MD5 (ssp/ssp-sandisk-extremepro-32gb-230720191843.img) = 6042ff8445bf88921d1f6e71146d3e0d


❯ diskutil list /dev/disk4
/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.9 GB    disk4
   1:       Microsoft Basic Data                         4.1 MB     disk4s1
   2:       Microsoft Basic Data                         65.5 KB    disk4s2
   3:       Microsoft Basic Data                         4.2 MB     disk4s3
   4:       Microsoft Basic Data                         4.2 MB     disk4s4
   5:       Microsoft Basic Data                         4.2 MB     disk4s5
   6:       Microsoft Basic Data BOOT                    26.7 GB    disk4s6
   7:       Microsoft Basic Data                         3.1 GB     disk4s7
                    (free space)                         2.1 GB     -


❯ diskutil info /dev/disk4
   Device Identifier:         disk4
   Device Node:               /dev/disk4
   Whole:                     Yes
   Part of Whole:             disk4
   Device / Media Name:       Built In SDXC Reader

   Volume Name:               Not applicable (no file system)
   Mounted:                   Not applicable (no file system)
   File System:               None

   Content (IOContent):       GUID_partition_scheme
   OS Can Be Installed:       No
   Media Type:                Generic
   Protocol:                  Secure Digital
   SMART Status:              Not Supported

   Disk Size:                 31.9 GB (31914983424 Bytes) (exactly 62333952 512-Byte-Units)
   Device Block Size:         512 Bytes

   Media OS Use Only:         No
   Media Read-Only:           No
   Volume Read-Only:          Not applicable (no file system)

   Device Location:           Internal
   Removable Media:           Removable
   Media Removal:             Software-Activated

   Solid State:               Info not available
   Virtual:                   No

I also verified the UUID of the partition specified in the extlinux.conf:

❯ cat extlinux/extlinux.conf
label kernel-4.4
    kernel /zImage
    fdt /rk3288-percussa-engine-euro.dtb
    append  earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=D12AD4F6-2AE1-4071-B747-8807FD16E0DC rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3
❯ diskutil info /dev/disk4s7
   Device Identifier:         disk4s7
   Device Node:               /dev/disk4s7
   Whole:                     No
   Part of Whole:             disk4

   Volume Name:
   Mounted:                   No

   Partition Type:            Microsoft Basic Data
   File System Personality:   MS-DOS
   Type (Bundle):             msdos
   Name (User Visible):       MS-DOS (FAT)

   OS Can Be Installed:       No
   Media Type:                Generic
   Protocol:                  Secure Digital
   SMART Status:              Not Supported
   Disk / Partition UUID:     D12AD4F6-2AE1-4071-B747-8807FD16E0DC
   Partition Offset:          26672627712 Bytes (52094976 512-Byte-Device-Blocks)

   Disk Size:                 3.1 GB (3145728000 Bytes) (exactly 6144000 512-Byte-Units)
   Device Block Size:         512 Bytes

   Volume Total Space:        0 B (0 Bytes) (exactly 0 512-Byte-Units)
   Volume Free Space:         0 B (0 Bytes) (exactly 0 512-Byte-Units)

   Media OS Use Only:         No
   Media Read-Only:           No
   Volume Read-Only:          Not applicable (not mounted)

   Device Location:           Internal
   Removable Media:           Removable
   Media Removal:             Software-Activated

   Solid State:               Info not available

Finally, some checksums of the core files:

❯ md5 zImage rk3288-percussa-engine-euro.dtb SYNTHOR
MD5 (zImage) = b899c61572b20474499cf2649ec27c9c
MD5 (rk3288-percussa-engine-euro.dtb) = e63a21c4886de9a8ab48f0c8d08157df
MD5 (SYNTHOR) = 5ef780ca9e110680042584acf81d0b6c

Any other ideas @bert ? Is it possible that the eMMC is corrupted or something? I couldn’t find instructions anywhere to reflash that for SSP specifically, but I did find https://wiki.t-firefly.com/ROC-RK3328-CC/flash_emmc.html and I’m willing to try that if it could help. Another idea: could you please build a new SDCard disk image with all the latest updates? My HW serial number is 172 if that makes any difference. Thanks!

did you try to mount the rootfs? that is going to be the real ‘tell tale sign’

as I said, I don’t think the emmc is used (currently)
you can see that two sd card partitions are used:

/dev/mmcblk0p7 on / type ext4 (rw,relatime,stripe=32753,data=ordered)
/dev/mmcblk0p6 on /media/linaro/SYNTHOR type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,user)

p06 id the FAT partition, that is also being booted from, we can see this since here we can also see the zImage and splash etc.

this would normally load the rootfs , you can see this in your log

reading /extlinux/extlinux.conf

you can attempt to load that partition on any linux system (linux is needed since its ext4) , and so that will verify if the partition can be mounted… I suspect you’ll find it cannot.

unfortunately I don’t have the image here any more, so I cannot do an MD5 on it.
… and if I download, then I don’t have a spare sdcard to check that my download worked -arghh!

my checksum for image etc look the same

MD5 (zImage) = b899c61572b20474499cf2649ec27c9c
MD5 (rk3288-percussa-engine-euro.dtb) = e63a21c4886de9a8ab48f0c8d08157df
MD5 (SYNTHOR) = 3501ec9121a9893a25f544fbee6220a1

SYNTHOR is different since I have latest, but is irrelevant, as you are not getting that far.

but his all tells us nothing of the state of the rootfs, which is where I think it all goes wrong :frowning:

the image in your first link definitely used to work fine… many of us used to update the ssp sdcard.
a zip file should means its integrity is ok,(?)
Balena Etcher also verifies the write is ok to the sdcard.

I don’t think Id bother trying to boot another dist, I suspect thats not going to get you too far without quite a bit of work…
bare in mind, the SSP is designed as a ‘product’ rather than as general purpose computer… so its not really expected that end-users are going to install their own distributions, and there is not documentation to support that process. (which I think is reasonable, given main use-case and dev resources etc)

so yeah, Id be trying to load that rootfs on a linux box… and see what’s going on…

sorry, I don’t have a serial console attached (and not adding one :wink: ) to my SSP , so Im not entirely sure of the full booting sequence over the console, and so what to expect… all I can see is booting once the rootfs is mounted and initd is run. (via dmesg etc)… but I don’t think you’re getting that far.
(though that would be worth checking if you can mount rootfs)

my guess, is its going to be something very tedious … like the image you have is corrupted.
either by writing process to card or when it was downloaded.
(its a real shame we don’t have an MD5 of it to confirm)

as tedious as it may be, perhaps try to download it again?

1 Like

Thanks again for your help. I’m on one of my Ubuntu PCs now and I can mount rootfs and BOOT OK. I reflashed a few of the cards a few times using Etcher under Linux. Just for kicks, I also ran the “check” tool (which runs fsck under the hood) in gparted against both the BOOT and rootfs partitions. That didn’t make a difference, unfortunately.

fdisk, parted, and blkid output:

   root@pop-os:~# fdisk -l /dev/sdc
    Disk /dev/sdc: 29.72 GiB, 31914983424 bytes, 62333952 sectors
    Disk model: uSD UHS2 RDR    
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 00042021-0408-4601-9DCC-A8C51255994F

    Device        Start      End  Sectors  Size Type
    /dev/sdc1        64     8063     8000  3.9M Microsoft basic data
    /dev/sdc2      8064     8191      128   64K Microsoft basic data
    /dev/sdc3      8192    16383     8192    4M Microsoft basic data
    /dev/sdc4     16384    24575     8192    4M Microsoft basic data
    /dev/sdc5     24576    32767     8192    4M Microsoft basic data
    /dev/sdc6     32768 52092927 52060160 24.8G Microsoft basic data
    /dev/sdc7  52094976 58238975  6144000  2.9G Microsoft basic data 

\parted:

   root@pop-os:~# parted /dev/sdc
    GNU Parted 3.4
    Using /dev/sdc
    Welcome to GNU Parted! Type 'help' to view a list of commands.
    (parted) print                                                            
    Model: Lexar uSD UHS2 RDR (scsi)
    Disk /dev/sdc: 31.9GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    Disk Flags: 

    Number  Start   End     Size    File system  Name       Flags
     1      32.8kB  4129kB  4096kB               loader1    msftdata
     2      4129kB  4194kB  65.5kB               reserved1  msftdata
     3      4194kB  8389kB  4194kB  fat32        reserved2  msftdata
     4      8389kB  12.6MB  4194kB               loader2    msftdata
     5      12.6MB  16.8MB  4194kB               atf        msftdata
     6      16.8MB  26.7GB  26.7GB  fat32        boot       legacy_boot, msftdata
     7      26.7GB  29.8GB  3146MB  ext4         rootfs     msftdata

    (parted)      

\blkid

root@pop-os:~# blkid /dev/sdc
/dev/sdc: PTUUID="00042021-0408-4601-9dcc-a8c51255994f" PTTYPE="gpt"
root@pop-os:~# blkid /dev/sdc*
/dev/sdc: PTUUID="00042021-0408-4601-9dcc-a8c51255994f" PTTYPE="gpt"
/dev/sdc1: PARTLABEL="loader1" PARTUUID="d117f98e-6f2c-d04b-a5b2-331a19f91cb2"
/dev/sdc2: PARTLABEL="reserved1" PARTUUID="25718777-d0ad-7443-9e60-02cb591c9737"
/dev/sdc3: UUID="3665-6331" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="reserved2" PARTUUID="8a4bb8b4-e304-ae48-8536-aff5c9c495b1"
/dev/sdc4: PARTLABEL="loader2" PARTUUID="08992135-13c6-084b-9322-3391ff571e19"
/dev/sdc5: PARTLABEL="atf" PARTUUID="333a128e-d3e3-b94d-92f4-d3ebd9b3224f"
/dev/sdc6: LABEL="BOOT" UUID="9E97-5BC5" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="boot" PARTUUID="893fc68d-779c-4032-8dce-a85efed2969b"
/dev/sdc7: LABEL="rootfs" UUID="9bc3eeff-a58e-437d-9762-59ce00ff3f21" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="d12ad4f6-2ae1-4071-b747-8807fd16e0dc"

I also noticed that the partitions had the “msftdata” flag set, so I tried unsetting that in gparted, which worked for all except one partition. This also made no difference on the SSP, however.

I noticed two spaces in the line in extlinux.conf, between “append” and “earlyprintk”. Fixing this made no difference.

append  earlyprintk console=tty1 console=ttyS2,115200n8 rw root=PARTUUID=D12AD4F6-2AE1-4071-B747-8807FD16E0DC rootfstype=ext4 init=/sbin/init acpi=off isolcpus=1,2,3

I also tried appending loglevel=7 and loglevel=8 at the end of the append line in extlinux.conf, which had no effect to what was displayed over serial console.

Lastly, I tried powering the +12V only off of a lab power supply, which also made no difference. I have a second Intellijel Palette (62HP) on the way since I ended up getting a few more other modules than fit into the 104HP (again, they’re all currently unplugged except the SSP), so I’ll give that a shot when it gets in as well.

I’ve seen lots of SD card corruption dealing with Raspberry Pis and power cycling at work, so I’m fairly convinced that this isn’t a hardware issue, but without a different image to try (I checked a few other threads and they all seemingly link to the latest ssp-sandisk-extremepro-32gb-230720191843.zip image), I’m a bit out of options on that front.

If the other headers on the back of the SSP have JTAG or SWD, I can try hooking OpenOCD up to it via a GreatFET One as well, or if there are other kernel options that might show more debug info, that’d be great.

me too, but using a fresh card image always works…

so there is something wrong with the image being put on the card…
I guess its possible that the download image has been corrupted on amazon servers, which is about all that is left now…

Im concerned that the boot image is obviously working on the ssp, and that the rootfs appears mountable on another system… since its then unclear why you don’t see init start running.
… the fact that the bootloader seems to cycle, definitely felt like it couldn’t get to start /sbin/init off the rootfs

but this is all really a bit of a moot point…
basically either the image that you can downloaded is ‘useable’ or not, if its corrupt, no amount of tinkering is going to fix it.
bare in mind , it used to work… so its not like there is something wrong with it ‘technically’.

not really sure what to suggest…
ideally, you’d have a known working sdcard, or be able to test it on another SSP… but thats not so easy :wink:


only thing I can do is to try to reproduce…

so, Im now downloading the SSP image off Amazon servers
Ive realised Ive got some large sdcards (128gb!) in my drones… so I can write to one of those for test purposes… they are only ‘ultras’ (which is a step below iirc) but should be enough for testing (ive used on rPI before)
could be a few hours, but at least we know if it doesn’t work for me… then its possible the image is not good.

(I can also then get an MD5 of the image, so we can confirm this matches yours)

I’ll let you know once I have anything of interest…
(downloading is going very slowly !)

Thanks so much for trying to repro this! FWIW I’ve also tried downloading the zip file through a work VPN just to see if anything on my local network was causing a problem. It’s also possible that something with Etcher is messing up the image now, as I am trying using latest Etcher across windows / linux / Mac. I’ll look up tomorrow how to write the image out without using Etcher to see if that makes any difference.

you can use dd , basically

 sudo dd if=/path/to/inputFile.img of=/dev/mydisk bs=1024k

Bela has a good tutorial on this

https://learn.bela.io/using-bela/bela-techniques/managing-your-sd-card/

ok, I have some bad news for you :frowning:

my download works fine!

here’s my checksum, which is identical to yours, so the img and unzip seems fine to me.

MD5 (ssp-sandisk-extremepro-32gb-230720191843.img) = 6042ff8445bf88921d1f6e71146d3e0d

I then flashed onto a sandisk extreme (128gb, its what I had) , my process was as described in the various posts.

a) download image as per above link
b) unzip using “The unarchiver” on my Mac (11.6.1, M1)
(this is important I noticed other unzip apps did not like it for some reason)
c) flash using latest Balena Etcher (I downloaded this morning)
d) pop it into SSP

did that, and it ran first time, and brought up the initial SSP patch…

so, I think your image file is fine (otherwise MD5 would differ)
I guess that leaves only possible error in:
a) writing to sd card
b) sdcard issue
c) some hardware issue on ssp.

my main concern is as before…
rootfs is mountable on another linux system, id not expect that to work if it was corrupted.
etcher verifies its write, I can’t see that passing if there was an issue with writing the sdcard.
(and Ive seen etcher fail verifying in the past when I had a dodgy sdcard)

given you have tried other sdcards etc, im really not sure what to suggest!?


edit: a complete aside… and more to address my own curiosity :slight_smile:
I just noticed the sdcard delivered with the SSP is an sandisk extreme , not extreme pro as you might think by the image name … these are microSDXC UHS-I , U3/V30 … specs

not that any of this will matter for booting, it would work with pretty much any 32+gb sdcard…
this would only really come into play if we started streaming audio on/off the sdcard, and then you might get poor performance, rather than it not work.