Thanks bodhi. It is hanging occasionally on mtest, and giving me some errors, so I think the RAM is flaky. Unfortunately the RAM is soldered on this model, so I think I'm out of luck. Thanks so much for all your help in helping me troubleshoot!by mesnyder1 - uBoot
bodhi, Unfortunately same results. Press Ctrl+C to abort autoboot in 3 second ALPINE_DB> dhcp al_eth0 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 *** Unhandled DHCP Option in OFFER/ACK: 119 *** Unhandled DHCP Option in OFFER/ACK: 119 DHCP client bound to address 10.0.0.236 ALPINE_DB> setenv bootargs consoleby mesnyder1 - uBoot
$ file zImage.5 zImage.5: u-boot legacy uImage, Linux-3.2.40, Linux/ARM, OS Kernel Image (Not compressed), 2307304 bytes, Thu Nov 12 09:17:41 2015, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0xBADB1C4A, Data CRC: 0xA418269E $ mkimage -l zImage.5 Image Name: Linux-3.2.40 Created: Thu Nov 12 03:17:41 2015 Image Type: ARM Linux Kernel Image (uncompressed) Databy mesnyder1 - uBoot
bodhi, zImage.5 and rd.bin.5 both came from the Synology website, I extracted them from DSM version 5 image, DSM_DS416_5644.pat, then extracted them with 7za. I then renamed them with the .5 suffix to differentiate between the different versions I had downloaded. I tried these files from DSM6 and DSM7 as well, but didn't get as far, those were giving me the 'invalid instruction'by mesnyder1 - uBoot
Here you go. 1st test Press Ctrl+C to abort autoboot in 3 second ALPINE_DB> setenv bootargs console=ttyS0,115200 earlyprintk=serial ALPINE_DB> tftpboot 0x2000000 zImage.5 al_eth0 Waiting for PHY auto negotiation to complete....... done *** ERROR: `ipaddr' not set ALPINE_DB> dhcp BOOTP broadcast 1 BOOTP broadcast 2 *** Unhandled DHCP Option in OFFER/ACK: 119 *** Unhandby mesnyder1 - uBoot
After a clean boot (no tftp downloads), these both fail. Is that what you meant? ALPINE_DB> bootm 0x8000000 0x7500000 Wrong Image Format for bootm command ERROR: can't get kernel image! ALPINE_DB> bootm 0x8000000 - 0x3B84008 Wrong Image Format for bootm command ERROR: can't get kernel image!by mesnyder1 - uBoot
bohdi, Thanks for building that! Unfortunately it still hangs. I tried with kernels from both DMS 7 and DSM 5. Here's the output from using the DSM 5 kernel. I don't have a cross-compiler environment setup. I could do that, but if you already have that, would you be able to compile it for me? Annapurna Labs stage 2: stage2_eth3_ram_loader v1.49.3 Executing next! Annapurnaby mesnyder1 - uBoot
Here you go. I also tried a few commands that display data. ALPINE_DB> help fdt fdt - flattened device tree utility commands Usage: fdt addr [-c] <addr> [<length>] - Set the fdt location to <addr> fdt boardsetup - Do board-specific set up fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it activby mesnyder1 - uBoot
I tried this after reset and after downloading over TFTP as well. Same results:: ALPINE_DB> bootz 8000000 7500000 3B84008 Bad Linux ARM zImage magic! ALPINE_DB>by mesnyder1 - uBoot
And here's version and environment as well. ALPINE_DB> version U-Boot 2013.10-alpine_db-1.49.4-SYNO-768e80b-2016-01-04 (Jan 04 2016 - 18:44:17) arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-2012.09-20120921 - Linaro GCC 2012.09) 4.7.2 20120910 (prerelease) GNU ld (crosstool-NG linaro-1.13.1-2012.09-20120921 - Linaro GCC 2012.09) 2.22 ALPINE_DB> printenv arch=arm ata_by mesnyder1 - uBoot
Here you go. ALPINE_DB> help ? - alias for 'help' WOLTest - Wake On Lan u-boot testing base - print or set address offset bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootmenu- ANSI terminal bootmenu bootp - boot iby mesnyder1 - uBoot
bodhi, It must be loading alpine_db.dtb from flash. That file is not in any of the DSM files from Synology, so if it is corrupt in flash, I don't know where to get another copy. There is a file uboot_DS416.bin, maybe it's embedded there, if I can find the right offset. I've looked through several DSM version downloads, and haven't been able to find alpine_db.dtb. I dby mesnyder1 - uBoot
Sure, here you go. I'm not sure I'm using the right boot command though. I used 'bootm 8000000 7500000 3B84008'. Thanks for your help! Annapurna Labs stage 2: stage2_eth3_ram_loader v1.49.3 Executing next! Annapurna Labs stage 2: stage2.5_loader v1.49.3 SPD I2C Address:00000057 Executing next! Stage 3 2013.10-alpine_spl-1.49.4-00666-gccfe35f (Sep 08 2014 - 09:by mesnyder1 - uBoot
Thanks bodhi. I tried adding that, and I am getting additional output. I'm actually seeing inconsistent behavior, which leads me to suspect a hardware issue, maybe bad RAM. So it could be that this is unrecoverable. These are some of the results I've gotten. Note the "Lifux" misspelling, which seems to occur on the 2nd or 3rd reset after power-on. Uncompressing Lifux>.by mesnyder1 - uBoot
I've gotten a little further. I think I've figured out the correct commands to transfer zImage and rd.bin, then boot. Now getting stuck at "Uncompressing Linux...". It's been stuck here about 45 minutes so far. ALPINE_DB> setenv serverip 10.0.0.17 ALPINE_DB> dhcp al_eth0 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 BOOTP broaby mesnyder1 - uBoot
I've got a DS416 that won't boot, but a different issue than @VectraT from the DS414 unbricking topic. I get a constant flashing blue light, and the reset button won't work. I connected to the serial console, and initially after a few retries I got: Starting kernel ... Uncompressing Linux... LZMA data is corrupt -- System halted I tried following the directions eby mesnyder1 - uBoot
I've got a DS416 that won't boot, but a different issue than @VectraT. I get a constant flashing blue light, and the reset button won't work. I connected to the serial console, and initially after a few retries I got: Starting kernel ... Uncompressing Linux... LZMA data is corrupt -- System halted I tried following the directions earlier for the DS414, and was abby mesnyder1 - uBoot