Skip to content

Unable to upgrade to 2.1.0 #241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Slyrc opened this issue Feb 7, 2025 · 6 comments
Open

Unable to upgrade to 2.1.0 #241

Slyrc opened this issue Feb 7, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@Slyrc
Copy link

Slyrc commented Feb 7, 2025

I have a Turing Pi 2.4 which is currently running 2.0.5

If I upgrade over ota to 2.1.0 the whole software bricks and interestingly shows version 1.0.0 on the website.
After that basically it is useless. I can not connect via ssh anymore.

I also flashed an SD card with 2.1.0 -> Same result here as well. Stuck and won't go anywhere. Only difference here is that I can not even open the webpage.

Only thing worked for me was using an SD card with 2.0.5 again to go back.

Also LED at node 1 is constantly flashing. Not sure if this was here before?
@Slyrc Slyrc added the bug Something isn't working label Feb 7, 2025
@Slyrc
Copy link
Author

Slyrc commented Feb 8, 2025 •
edited
Loading

Some more input here:

Here is the output of 2.0.5 starting (Even if there are some errors it still starts and I can login over ssh and the web ui)

U-Boot SPL 2024.01-rc1 (Nov 28 2023 - 13:50:37 +0000)
DRAM: 128 MiB
Trying to boot from sunxi SPI

U-Boot 2024.01-rc1 (Nov 28 2023 - 13:50:37 +0000) Turing Machines, Inc.

CPU:   Allwinner R528 (SUN8I)
Model: Turing Machines Turing Pi 2 BMC
DRAM:  128 MiB
Core:  53 devices, 23 uclasses, devicetree: separate
WDT:   Not starting watchdog@20500a0
MMC:   mmc@4020000: 0
Loading Environment from UBI... ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "ubi", size 127 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1016, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 7/5, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 449, total reserved PEBs: 567, PEBs reserved for bad PEB handling: 20
Read 65536 bytes from volume uboot-env to 47d36c00
OK
In:    serial@2500c00
Out:   serial@2500c00
Err:   serial@2500c00
Net:   eth0: ethernet@4500000
gpio: pin PG13 (gpio 205) value is 0
gpio: pin PG13 (gpio 205) value is 0
Setting bus to 0
Error writing the chip: 37812248
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Button key1 state: off
Hit any key to stop autoboot:  0 
Boot device: ubi
Boot mode: normalboot
Scanning ubi 0:rootfs...
Running U-Boot script: /boot/boot.scr.uimg

With SD card and firmware 2.1.0 I am greeted with that while installing:

U-Boot SPL 2024.01 (Jan 17 2025 - 16:59:07 +0000)
DRAM: 128 MiB
Error: reading EEPROM 37812248
Error(240f818): invalid board info, defaulting to version 0x1100. crc=0 expected=1c662483 ver=0
Trying to boot from MMC1

U-Boot 2024.01 (Jan 17 2025 - 16:59:07 +0000) Turing Machines, Inc.

CPU:   Allwinner R528 (SUN8I)
Model: Turing Pi 2 (v2.4)
DRAM:  128 MiB
Core:  75 devices, 25 uclasses, devicetree: fit
WDT:   Not starting watchdog@20500a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... OK
In:    serial@2500c00
Out:   serial@2500c00
Err:   serial@2500c00
Net:   eth0: ethernet@4500000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
, eth1: usb_ether
Setting bus to 0
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Error writing the chip: 40957960
Button key1 state: off
Hit any key to stop autoboot:  0 
Boot device: mmc
Boot mode: normalboot
Scanning mmc 0:1...
Running U-Boot script: /boot/boot.scr.uimg
1187 bytes read in 4 ms (289.1 KiB/s)
## Executing script at 41900000
Checking /install.txt...
...exists: entering installer
Error: tpi_board_info: invalid CRC
4792500 bytes read in 1748 ms (2.6 MiB/s)
729754 bytes read in 124 ms (5.6 MiB/s)
## Loading kernel from FIT Image at 42000000 ...
   Using 'config-v2.4.0' configuration
   Trying 'kernel6_8' kernel subimage
     Description:  turingpi 6.8.12
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x42000910
     Data Size:    4691840 Bytes = 4.5 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x41000000
     Entry Point:  0x41000000
     Hash algo:    sha1
     Hash value:   5bfc8ef5c5f496eeaf4a1016a391408fc73bdcc2
   Verifying Hash Integrity ... sha1+ OK
## Loading init Ramdisk from Legacy Image at 41c00000 ...
   Image Name:   
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    729690 Bytes = 712.6 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Loading fdt from FIT Image at 42000000 ...
   Using 'config-v2.4.0' configuration
   Trying 'fdt-v2.4.0' fdt subimage
     Description:  sun8i-t113s-turing-pi2-v2.4.0
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x4247a090
     Data Size:    32546 Bytes = 31.8 KiB
     Architecture: ARM
     Load Address: 0x41800000
     Hash algo:    sha1
     Hash value:   e6c4319d49f6d4c815162aab168dbdf08fc46f45
   Verifying Hash Integrity ... sha1+ OK
   Loading fdt from 0x4247a090 to 0x41800000
   Booting using the fdt blob at 0x41800000
Working FDT set to 41800000
   Loading Kernel Image
   Loading Ramdisk to 46c6c000, end 46d1e25a ... OK
   Loading Device Tree to 46c61000, end 46c6bf21 ... OK
Working FDT set to 46c61000

Starting kernel ...

** 5 printk messages dropped **
[    2.648635] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    4.728622] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    6.968630] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    6.975214] realtek-smi 0-005c: failed to read chip id and version: -110
[    6.981961] realtek-smi 0-005c: unable to detect switch
[    9.048632] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0

 _____ _   _ ____  ___ _   _  ____
|_   _| | | |  _ \|_ _| \ | |/ ___|
  | | | | | | |_) || ||  \| | |  _
  | | | |_| |  _ < | || |\  | |_| |
  |_|  \___/|_| \_\___|_| \_|\____|

This utility will perform a fresh installation of the Turing Pi 2 BMC firmware.

Note that this will ERASE ALL USER DATA stored on the Turing Pi 2 BMC, thus
restoring back to factory defaults. Do NOT proceed unless you have first backed
up any files that you care about!

If you wish to confirm the operation and proceed, either:
1) Type 'CONFIRM' at the below prompt
2) Press one of the front panel buttons (POWER or RESET), or the KEY1 button on
   the Turing Pi 2 board itself, three times in a row

If you are here in error, please remove the microSD card from the Turing Pi 2
board and reset the BMC.

Type "CONFIRM" to continue: [   11.208330] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   13.288321] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   15.368322] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   17.448321] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   19.528318] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   21.608328] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
CONFIRM
 |    23.688360] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
 | Installing BMC firmware (2s)
 /    27.848360] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
 / Installing BMC firmware (1s)
 / Installing BMC firmware (2s)
 / Installing BMC firmware (2s)
 - Installing BMC firmware (4s)
 - Installing BMC firmware (5s)
 \ Installing BMC firmware (7s)
[+] DONE: Please remove the microSD card and reset the BMC.
[   42.408338] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   44.488322] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   46.568321] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   48.648321] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   50.728319] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   52.808318] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   54.888320] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0

After reboot with 2.1.0 I am able to login over uart. Seems like it does not get an IP address which is the case with 2.0.5 but not with 2.1.0

@svenrademakers
Copy link
Collaborator

It seems like you have some hardware issues; more specifically I2C-0 bus seems to be unresponsive. This part of the hardware got enabled on v2.1.0 so it explains why downgrading to 2.0.5 works. I would chech if you can reach out to turingpi on their website and see if they can do anything for you

@svenrademakers
Copy link
Collaborator

do you have any usb cables attached to the board? its worth a shot to completely take of the power off the board with all peripherals detached.

@Slyrc
Copy link
Author

Slyrc commented Feb 11, 2025

Good to know. I will try to reach out to them. Thanks!

@Slyrc
Copy link
Author

Slyrc commented Feb 11, 2025

Well I removed everything from the board including the battery. Waited a few minutes and the tried again. Seems like I am not lucky here.

@Slyrc
Copy link
Author

Slyrc commented Feb 11, 2025

Do you maybe know where this part is located on the board? Maybe it can be checked and repaired/replaced?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@svenrademakers @Slyrc