question

mitjastachowiak avatar image
mitjastachowiak asked

ColorControl lost Connection to MPPTs, broke after firmware-flash

Hello,

a few days ago, my ColorControl lost the connection to the BlueSolar MPPTs. After reboot, it worked for some seconds an then the values from MPPTs were not longer updated. In ESS-Mode they stop working. I tried to connect one MPPT with USB-VE.Direct cable, but it also just worked for a few seconds.

I then tried to flash the latest firmware. Was 2.18 before and I installed 2.87 from SD-Card. But after the installation-reboot, the ColorControl did not start anymore, just hangs in bootscreen. After more than one hour, I decided to fore a new reboot, but it's not working anymore.

I used the Serial Console to connect to the device, enabled the kernel-boot-messages and this is the last printed output:

starting resolv.conf manager: resolv-watch... [   13.953216] device eth0 entered promiscuous mode
done.
Starting crond: OK
[   14.688568] UBIFS error (ubi0:2 pid 445): ubifs_scan: garbage
[   14.694427] UBIFS error (ubi0:2 pid 445): ubifs_scanned_corruption: corruption at LEB 76:73728
[   14.703216] UBIFS error (ubi0:2 pid 445): ubifs_scanned_corruption: first 8192 bytes from LEB 76:73728
[   14.719329] UBIFS error (ubi0:2 pid 445): ubifs_scan: LEB 76 scanning failed
[   14.726501] UBIFS warning (ubi0:2 pid 445): ubifs_ro_mode.part.0: switched to read-only mode, error -117
[   14.736114] CPU: 0 PID: 445 Comm: connmand Not tainted 5.10.42-venus-8 #1
[   14.742980] Hardware name: Generic AM3517 (Flattened Device Tree)
[   14.749176] [<c010be0c>] (unwind_backtrace) from [<c010a168>] (show_stack+0x10/0x14)
[   14.756988] [<c010a168>] (show_stack) from [<c0355558>] (ubifs_ro_mode.part.0+0x40/0x48)
[   14.765197] [<c0355558>] (ubifs_ro_mode.part.0) from [<c0361288>] (ubifs_garbage_collect+0x214/0x39c)
[   14.774536] [<c0361288>] (ubifs_garbage_collect) from [<c03489cc>] (make_reservation+0x124/0x424)
[   14.783508] [<c03489cc>] (make_reservation) from [<c0349694>] (ubifs_jnl_write_data+0x108/0x2ac)
[   14.792419] [<c0349694>] (ubifs_jnl_write_data) from [<c034c7f8>] (do_writepage+0x98/0x260)
[   14.800872] [<c034c7f8>] (do_writepage) from [<c01f2fb4>] (__writepage+0x14/0x8c)
[   14.808471] [<c01f2fb4>] (__writepage) from [<c01f4180>] (write_cache_pages+0x178/0x3d4)
[   14.816650] [<c01f4180>] (write_cache_pages) from [<c01f57e8>] (do_writepages+0xa8/0xec)
[   14.824890] [<c01f57e8>] (do_writepages) from [<c01eccc0>] (__filemap_fdatawrite_range+0xb0/0xd0)
[   14.833892] [<c01eccc0>] (__filemap_fdatawrite_range) from [<c01ece34>] (file_write_and_wait_range+0x48/0x98)
[   14.843933] [<c01ece34>] (file_write_and_wait_range) from [<c034bcc4>] (ubifs_fsync+0x40/0xb4)
[   14.852630] [<c034bcc4>] (ubifs_fsync) from [<c0278068>] (do_fsync+0x3c/0x70)
[   14.859893] [<c0278068>] (do_fsync) from [<c0100060>] (ret_fast_syscall+0x0/0x54)
[   14.867462] Exception stack(0xc2a9dfa8 to 0xc2a9dff0)
[   14.872619] dfa0:                   00000000 b6f476d0 00000008 00000058 24051905 00000000
[   14.880889] dfc0: 00000000 b6f476d0 0088cc10 00000076 00000008 b6f476e0 0088b000 00000000
[   14.889160] dfe0: 41e5e03c be989b00 41d868b4 41b20088
[   14.894317] UBIFS error (ubi0:2 pid 445): make_reservation: cannot reserve 150 bytes in jhead 2, error -117
[   14.904205] UBIFS error (ubi0:2 pid 445): do_writepage: cannot write page 0 of inode 1398313, error -117
[   14.915863] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
[   14.925720] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 1398311, error -30
[   14.991394] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
[   15.001251] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 1398312, error -30
[   15.058044] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
[   15.067810] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 67, error -30
Checking available software versions...
Active rootfs: 2
Active version: 20220531142416 v2.87
[   16.148559] UBIFS (ubi0:0): Mounting in unauthenticated mode
[   17.467224] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs1", R/O mode
[   17.475799] UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   17.485900] UBIFS (ubi0:0): FS size: 208373760 bytes (198 MiB, 1615 LEBs), journal size 9033728 bytes (8 MiB, 71 LEBs)
[   17.496704] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
[   17.502624] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 921B723C-D0FC-4876-BB2D-0A4AFF5C863F, small LPT model
Backup version: 20180916222247 v2.18
[   18.723663] UBIFS (ubi0:0): un-mount UBI device 0
dbus-daemon[386]: [system] Activating service name='fi.w1.wpa_supplicant1' requested by ':1.2' (uid=0 pid=445 comm="connmand --nodnsproxy --nodaemon ") (using servicehelper)
INIT: no more processes left in this runlevel
dbus-daemon[386]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
������������������������������������������������������������������������������������������������������������������

The strange characters at the end appear in two steps. When I then insert the SD-card, some more of this characters appear. It seems, they are simply console output but with wrong baud rate or so.

Have you ever seen this behavior before? Is the ColorControl simply broken or is there a chance to recover from this?

CCGX Color Control
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

0 Answers