Bootet nicht - Firmware über den RedBoot flashen (TFTP)

Antworten
rbudde
Beiträge: 1
Registriert: 14. Mai 2013 20:39
SqueezeBox: Radio
SqueezeBox: Radio

Bootet nicht - Firmware über den RedBoot flashen (TFTP)

Beitrag von rbudde »

Hallo!

Ich bin neu hier. Mein Name ist Robert, und ich besitze eine heile und eine defekte Squeezebox Radio.

Die (ausdrücklich als defekt verkaufte) Squeezebox Radio habe ich heute bekommen. Kurzer Test zeigte, dass das Radio elektrisch ok ist. Über die 10-polige Stiftleiste komme ich auf die Debug-Konsole und kann die Meldungen des RedBoot Bootloaders sehen.

(ganz nach unten scrollen, da kommen wohl die "Show-Stopper")

Code: Alles auswählen

++NAND: RCSR=54200902
Searching for BBT table in the flash ...
.
Found version 1 Bbt0 at block 1023 (0x7fe0000)
Block 0 is bad
Block 1 is bad
Block 45 is bad
Block 134 is bad
Block 135 is bad
Block 376 is bad
Block 378 is bad
Block 413 is bad
Block 427 is bad
Block 448 is bad
Block 465 is bad
Block 486 is bad
Block 519 is bad
Block 523 is bad
Block 524 is bad
Block 528 is bad
Block 566 is bad
Block 575 is bad
Block 576 is bad
Block 577 is bad
Block 578 is bad
Block 579 is bad
Block 580 is bad
Block 581 is bad
Block 582 is bad
Block 584 is bad
Block 585 is bad
Block 586 is bad
Block 587 is bad
Block 588 is bad
Block 589 is bad
Block 590 is bad
Block 591 is bad
Block 592 is bad
Block 593 is bad
Block 594 is bad
Block 595 is bad
Block 596 is bad
Block 597 is bad
Block 598 is bad
Block 599 is bad
Block 600 is bad
Block 601 is bad
Block 602 is bad
Block 603 is bad
Block 604 is bad
Block 605 is bad
Block 606 is bad
Block 607 is bad
Block 608 is bad
Block 609 is bad
Block 610 is bad
Block 611 is bad
Block 612 is bad
Block 613 is bad
Block 614 is bad
Block 615 is bad
Block 616 is bad
Block 617 is bad
Block 618 is bad
Block 619 is bad
Block 620 is bad
Block 621 is bad
Block 622 is bad
Block 623 is bad
Block 624 is bad
Block 625 is bad
Block 626 is bad
Block 627 is bad
Block 628 is bad
Block 629 is bad
Block 630 is bad
Block 631 is bad
Block 632 is bad
Block 633 is bad
Block 634 is bad
Block 635 is bad
Block 636 is bad
Block 637 is bad
Block 638 is bad
Block 639 is bad
Block 640 is bad
Block 641 is bad
Block 642 is bad
Block 643 is bad
Block 644 is bad
Block 645 is bad
Block 646 is bad
Block 647 is bad
Block 648 is bad
Block 649 is bad
Block 650 is bad
Block 651 is bad
Block 652 is bad
Block 653 is bad
Block 654 is bad
Block 655 is bad
Block 656 is bad
Block 657 is bad
Block 658 is bad
Block 659 is bad
Block 660 is bad
Block 661 is bad
Block 662 is bad
Block 663 is bad
Block 664 is bad
Block 665 is bad
Block 666 is bad
Block 667 is bad
Block 668 is bad
Block 669 is bad
Block 670 is bad
Block 671 is bad
Block 672 is bad
Block 673 is bad
Block 674 is bad
Block 675 is bad
Block 676 is bad
Block 677 is bad
Block 678 is bad
Block 679 is bad
Block 680 is bad
Block 681 is bad
Block 682 is bad
Block 683 is bad
Block 684 is bad
Block 685 is bad
Block 686 is bad
Block 687 is bad
Block 688 is bad
Block 689 is bad
Block 690 is bad
Block 691 is bad
Block 692 is bad
Block 693 is bad
Block 694 is bad
Block 695 is bad
Block 696 is bad
Block 697 is bad
Block 698 is bad
Block 699 is bad
Block 700 is bad
Block 701 is bad
Block 702 is bad
Block 703 is bad
Block 704 is bad
Block 714 is bad
Block 740 is bad
Block 757 is bad
Block 774 is bad
Block 791 is bad
Block 792 is bad
Block 795 is bad
Block 987 is bad
Block 1018 is bad
Block 1019 is bad
Total bad blocks: 156
.
Warning: nfc_read_region(addr=0x7f40000, block=1018): skipping bad
.
Warning: nfc_read_region(addr=0x7f60000, block=1019): skipping bad
..
Warning: nfc_read_region(addr=0x7f60000, block=1019): skipping bad
.**Warning** FLASH configuration checksum error or invalid key
Use 'fconfig -i' to [re]initialize database
FEC PHY: RTL8201EL
FEC: [ HALF_DUPLEX ] [ disconnected ] [ 10M bps ]:
Ethernet mxc_fec: MAC address 00:04:20:ff:ff:01
No IP info for device!
Unrecognized chip: 0xf8!!!
hardware reset by WDOG

Clock input is 24 MHz
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version FSL 200904 - built 16:56:15, Jan  5 2012

Platform: Logitech Baby (i.MX25 )  PASS 1.0 [x32 DDR]
System type 2070 revision 7
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x00000000-0x03f00000, [0x00095250-0x03ef1000] available
FLASH: 0x00000000 - 0x8000000, 1024 blocks of 0x00020000 bytes each.
RedBoot> ubi attach -f 0x80000 -l 0x07EC0000 -w 0x800 -e 0x20000 -s 0x200
scanning 1014 PEBs
..................................................................................skipping bad block 41
................................................................................................................................................................................skipping bad block 130
skipping bad block 131
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................skipping bad block 372
..skipping bad block 374
....................................................................skipping bad block 409
..........................skipping bad block 423
........................................skipping bad block 444
................................skipping bad block 461
........................................skipping bad block 482
................................................................skipping bad block 515
......skipping bad block 519
skipping bad block 520
......skipping bad block 524
..........................................................................skipping bad block 562
................skipping bad block 571
skipping bad block 572
skipping bad block 573
skipping bad block 574
skipping bad block 575
skipping bad block 576
skipping bad block 577
skipping bad block 578
..skipping bad block 580
skipping bad block 581
skipping bad block 582
skipping bad block 583
skipping bad block 584
skipping bad block 585
skipping bad block 586
skipping bad block 587
skipping bad block 588
skipping bad block 589
skipping bad block 590
skipping bad block 591
skipping bad block 592
skipping bad block 593
skipping bad block 594
skipping bad block 595
skipping bad block 596
skipping bad block 597
skipping bad block 598
skipping bad block 599
skipping bad block 600
skipping bad block 601
skipping bad block 602
skipping bad block 603
skipping bad block 604
skipping bad block 605
skipping bad block 606
skipping bad block 607
skipping bad block 608
skipping bad block 609
skipping bad block 610
skipping bad block 611
skipping bad block 612
skipping bad block 613
skipping bad block 614
skipping bad block 615
skipping bad block 616
skipping bad block 617
skipping bad block 618
skipping bad block 619
skipping bad block 620
skipping bad block 621
skipping bad block 622
skipping bad block 623
skipping bad block 624
skipping bad block 625
skipping bad block 626
skipping bad block 627
skipping bad block 628
skipping bad block 629
skipping bad block 630
skipping bad block 631
skipping bad block 632
skipping bad block 633
skipping bad block 634
skipping bad block 635
skipping bad block 636
skipping bad block 637
skipping bad block 638
skipping bad block 639
skipping bad block 640
skipping bad block 641
skipping bad block 642
skipping bad block 643
skipping bad block 644
skipping bad block 645
skipping bad block 646
skipping bad block 647
skipping bad block 648
skipping bad block 649
skipping bad block 650
skipping bad block 651
skipping bad block 652
skipping bad block 653
skipping bad block 654
skipping bad block 655
skipping bad block 656
skipping bad block 657
skipping bad block 658
skipping bad block 659
skipping bad block 660
skipping bad block 661
skipping bad block 662
skipping bad block 663
skipping bad block 664
skipping bad block 665
skipping bad block 666
skipping bad block 667
skipping bad block 668
skipping bad block 669
skipping bad block 670
skipping bad block 671
skipping bad block 672
skipping bad block 673
skipping bad block 674
skipping bad block 675
skipping bad block 676
skipping bad block 677
skipping bad block 678
skipping bad block 679
skipping bad block 680
skipping bad block 681
skipping bad block 682
skipping bad block 683
skipping bad block 684
skipping bad block 685
skipping bad block 686
skipping bad block 687
skipping bad block 688
skipping bad block 689
skipping bad block 690
skipping bad block 691
skipping bad block 692
skipping bad block 693
skipping bad block 694
skipping bad block 695
skipping bad block 696
skipping bad block 697
skipping bad block 698
skipping bad block 699
skipping bad block 700
..................skipping bad block 710
..................................................skipping bad block 736
................................skipping bad block 753
................................skipping bad block 770
................................skipping bad block 787
skipping bad block 788
....skipping bad block 791
..............................................................................................................................................................................................................................................................................................................................................................................................skipping bad block 983
............................................................scanning is finished
the layout volume was not found
Volume table error -22

RedBoot> ubi load -b 0x100000 kernel%{os_backup}
No volume 'kernel' found
RedBoot> exec -c %{os_cmdline}Warning: invalid entry address but still continue ...
entry=0x80008000, target=0x80008000
Base address unknown - use "-b" option
RedBoot>
Wenn ich http://wiki.slimdevices.com/index.php/F ... d_Recovery richtig verstehe, müsste ich per TFTP ein neues Firmware-Image flashen können. Jedoch weiß ich nicht, woher ich ein "ubi" für die "Baby-Plattform" (scheinbar das Squeezebox Radio) bekomme. Im http://downloads.slimdevices.com/Logite ... er_v7.7.2/ finde ich nur "bin"-Endungen.

Leider finde ich in den weiten des Internet keine Hinweise das Problem zu lösen...

Vielen Dank!

Grüße
Robert
Benutzeravatar
Penni
Beiträge: 770
Registriert: 12. November 2010 23:51
SqueezeBox: Duet
SqueezeBox: Classic
SqueezeBox: Radio
SqueezeBox: Boom
SqueezeBox: Touch
SqueezeBox Server läuft auf: max2play auf Raspberry Pi1
Wohnort: Bern

Re: Bootet nicht - Firmware über den RedBoot flashen (TFTP)

Beitrag von Penni »

rbudde hat geschrieben: Wenn ich http://wiki.slimdevices.com/index.php/F ... d_Recovery richtig verstehe, müsste ich per TFTP ein neues Firmware-Image flashen können. Jedoch weiß ich nicht, woher ich ein "ubi" für die "Baby-Plattform" (scheinbar das Squeezebox Radio) bekomme. Im http://downloads.slimdevices.com/Logite ... er_v7.7.2/ finde ich nur "bin"-Endungen.
Hallo Robert
Versuch es mal unter http://update.slimdevices.com/update/firmware/
Ob Du Dein Problem damit lösen kannst weiss ich nicht.

MfG, Penni d:-)
Vorgesetzte besitzen auf Grund ihrer Stellung das wertvolle Privileg, bezüglich ihrer Fehler und Schwächen angelogen zu werden. (hab' ich mir so gedacht)
Antworten