Re: [57north-discuss] Bricked Startech IP-KVM
On 19/01/2021 08:55, Lawrence wrote: Tony As U-boot tends to be built for the board and is very flexible it is possible to build it with a zero timeout on the boot prompt so it becomes impossible to enter interactive mode. Hi, Lawrence. Can't help thinking they did that on purpose :-( When you have it open also look for a JTAG connector, typically a 2*5 or 2*10 pin header as this will be another possible route into accessing the flash. (Looks as if maybe a 16 pin connector https://www.etoolsmiths.com/jtag-pinouts-and-connectors-for-powerpc/) OK + thx for that link. U-Boot probably has it's own partitions in the flash, commonly a partition for uboot and a partition for uboot confirguration. But also has default configuration built in so just erasing uboot config may not help. I've attached the boot logs from my 'bricked' SV841DUSBI IP-KVM and a working SV841DUSBI IP-KVM, which seems to have idenical firmware, and a diff of the boot logs, showing where the SV841DUSBI IP-KVM goes wrong. If in touch with startech them ask them whether it has a JTAG port or what do they use for factory programming. I have a variety of programming hardware. My Startech support contact has not relied since I told him I bought the IP-KVM off eBay, despite Startech's widely advertised lifetime support. Looking at the boot log the kernel looks OK and it is possibly the root filesystem that is the problem. Yes, I think you're right about that. Thanks for your helpful suggestions, Tony. -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk U-Boot 1.1.1 (Jan 11 2007 - 10:36:35) CPU: IBM PowerPC 405EP Rev. B at 200 MHz (PLB=100, OPB=50, EBC=50 MHz) IIC Boot EEPROM disabled PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 16 kB D-Cache DRAM: 32 MB FLASH: 8 MB MAC Address: 00:0e:c5:01:29:9e Load FPGA: 212392 bytes: Ok ## Booting image at 1000 ... Image Name: Linux-2.4.25 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:773504 Bytes = 755.4 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Linux version 2.4.25 (x@x) (gcc version 2.95.3 20010315 (release)) #1038 Fri Apr 18 14:27:17 EDT 2008 IBM Walnut port (C) 2000-2002 MontaVista Software, Inc. (sou...@mvista.com) Board customizations (C) 2002-6 Peter D. Gray. On node 0 totalpages: 8192 zone(0): 8192 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/mtdblock4 mtdparts=phys:1m(kern),128k(fpga),64k(unique),1m(user),5824k(cramfs),128k(boot) TYPE=J console=ttyS0,115200 Calibrating delay loop (skipped)... 199.88 BogoMIPS Memory: 30400k available (1412k kernel code, 464k data, 84k init, 0k highmem) Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) Inode cache hash table entries: 2048 (order: 2, 16384 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 8192 (order: 3, 32768 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd devfs: v1.12c (20020818) Richard Gooch (rgo...@atnf.csiro.au) devfs: boot_options: 0x1 i2c-core.o: i2c core module version 2.6.1 (20010830) i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830) i2c-proc.o version 2.6.1 (20010830) pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0xef600300 (irq = 0) is a 16550A ttyS01 at 0xef600400 (irq = 1) is a 16550A IBM gpio driver version 07.25.02 GPIO #0 at 0xc300d700 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) emac: IBM OCP EMAC Ethernet driver, version 2.1 Maintained by Benjamin Herrenschmidt mal0: Initialized, 4 tx channels, 2 rx channels eth0: IBM emac, MAC 00:0e:c5:01:29:9e eth0: Found Generic MII PHY (0x01) emac1: Can't find PHY. PPP generic driver version 2.4.2 PPP Deflate Compression module registered physmap flash device: 80 at 1000 phys: Found 1 x16 devices at 0x0 in 16-bit bank Amd/Fujitsu Extended Query Table at 0x0040 phys: CFI does not contain boot bank location. Assuming top. number of CFI chips: 1 cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. 6 cmdlinepart partitions found on MTD device phys Creating 6 MTD partitions on "phys": 0x-0x0010 : "kern" 0x0010-0x0012 : "fpga" 0x0012-0x0013 : "unique" 0x0013-0x0023 : "user" 0x0023-0x007e : "cramfs" 0x007e-0x0080 : "boot" IBM IIC driver
Re: [57north-discuss] Bricked Startech IP-KVM
Tony As U-boot tends to be built for the board and is very flexible it is possible to build it with a zero timeout on the boot prompt so it becomes impossible to enter interactive mode. When you have it open also look for a JTAG connector, typically a 2*5 or 2*10 pin header as this will be another possible route into accessing the flash. (Looks as if maybe a 16 pin connector https://www.etoolsmiths.com/jtag-pinouts-and-connectors-for-powerpc/) U-Boot probably has it's own partitions in the flash, commonly a partition for uboot and a partition for uboot confirguration. But also has default configuration built in so just erasing uboot config may not help. If in touch with startech them ask them whether it has a JTAG port or what do they use for factory programming. I have a variety of programming hardware. Looking at the boot log the kernel looks OK and it is possibly the root filesystem that is the problem. Lawrence On 18/01/2021 22:29, Tom Jones wrote: On Mon, Jan 18, 2021 at 10:23:42PM +, Tony Travis wrote: On 18/01/2021 22:15, Tom Jones wrote: [...] Can you break into u-boot? Hi, Tom. Not succeeded yet, but still trying... If you can get a u-boot prompt then you can probably dump the flash. >From u-boot, I don't see the normal 'press any key to interrupt boot' message so you might be out of luck. I know + that's disappointing :-( If you can share internals photos and a firmware image then we might be able to manually flash any spi eeproms. Risky, but might be worth it. OK, I'll pull it to bits again and have a look. I've emailed sou...@mvista.com and i...@mvista.com, asking for help. Cool, If you take it a part again please take pictures of everything. Ideally both sides of boards. It is hard to get part numbers to show in pictures so writing them down while the board is open can help. Some times they are really hard to read, so a photo with light coming at a particular angle can help and sometimes you have to try a range. I think this board is quite large, I would suggest one front and back and then the closest shots you can manage of all chips on the board. - Tom ___ 57north-discuss mailing list 57north-discuss@lists.57north.co http://lists.57north.co/listinfo/57north-discuss ___ 57north-discuss mailing list 57north-discuss@lists.57north.co http://lists.57north.co/listinfo/57north-discuss
Re: [57north-discuss] Bricked Startech IP-KVM
On Mon, Jan 18, 2021 at 10:23:42PM +, Tony Travis wrote: > On 18/01/2021 22:15, Tom Jones wrote: > > [...] > > Can you break into u-boot? > > Hi, Tom. > > Not succeeded yet, but still trying... > > > If you can get a u-boot prompt then you can probably dump the flash. > >>From u-boot, I don't see the normal 'press any key to interrupt boot' > > message so you might be out of luck. > > I know + that's disappointing :-( > > > If you can share internals photos and a firmware image then we might be > > able to manually flash any spi eeproms. Risky, but might be worth it. > > OK, I'll pull it to bits again and have a look. > > I've emailed sou...@mvista.com and i...@mvista.com, asking for help. > Cool, If you take it a part again please take pictures of everything. Ideally both sides of boards. It is hard to get part numbers to show in pictures so writing them down while the board is open can help. Some times they are really hard to read, so a photo with light coming at a particular angle can help and sometimes you have to try a range. I think this board is quite large, I would suggest one front and back and then the closest shots you can manage of all chips on the board. - Tom ___ 57north-discuss mailing list 57north-discuss@lists.57north.co http://lists.57north.co/listinfo/57north-discuss
Re: [57north-discuss] Bricked Startech IP-KVM
On 18/01/2021 22:15, Tom Jones wrote: [...] Can you break into u-boot? Hi, Tom. Not succeeded yet, but still trying... If you can get a u-boot prompt then you can probably dump the flash. From u-boot, I don't see the normal 'press any key to interrupt boot' message so you might be out of luck. I know + that's disappointing :-( If you can share internals photos and a firmware image then we might be able to manually flash any spi eeproms. Risky, but might be worth it. OK, I'll pull it to bits again and have a look. I've emailed sou...@mvista.com and i...@mvista.com, asking for help. Thanks, Tony. -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk ___ 57north-discuss mailing list 57north-discuss@lists.57north.co http://lists.57north.co/listinfo/57north-discuss
Re: [57north-discuss] Bricked Startech IP-KVM
On Mon, Jan 18, 2021 at 09:05:41PM +, Tony Travis wrote: > Hi, > > As you know, I accidentally 'bricked' my Startech SV841DUSBI IP-KVM > attempting to upgrade the firmware using the built-in Web GUI and > despite the best efforts of Startech product support they can't help me > to reload the firmware, which means my IP-KVM is now 'bricked' :-( > > However, I connected an RS232 null-modem to the DTE serial port of the > IP-KVM to see if the Startech Linux controller outputs any diagnostic > information - It does, and and I captured the Linux kernel boot log > attached below. > > Unfortunately, Linux does not boot successfully because the image is > corrupted... > > Does anybody know if the version of U-Boot installed on this board can > be used to reload the Linux firmware image over the serial port? > > I've not found a way of interrupting the boot to get interactive control > of U-Boot. Normally, you just press a key within the first few seconds, > but that doesn't seem to work on the board in my bricked IP-KVM... > Can you break into u-boot? If you can get a u-boot prompt then you can probably dump the flash. From u-boot, I don't see the normal 'press any key to interrupt boot' message so you might be out of luck. If you can share internals photos and a firmware image then we might be able to manually flash any spi eeproms. Risky, but might be worth it. - Tom ___ 57north-discuss mailing list 57north-discuss@lists.57north.co http://lists.57north.co/listinfo/57north-discuss
