16:34 <IoT-Maker> PaulFertser: No luck so far. Tried different ways of loading an image. Couldn't get u-boot loady to work in minicom/ymodem. I did it using kermit (ckermit) after creating a .kermrc config. But it is too slow. It takes more than 90 minutes to load 53mb file.

16:37 <IoT-Maker> Way faster but same result is loading in openocd using load_image, resume and starting in u-boot. But it always says my image is not an elf image. Either if i use the one i cropped from firmware file or the one emba extracted from firmware file.

16:41 <bencoh> well, if you extracted a kernel Image/zImage, then it's not ELF indeed

16:42 <bencoh> oh, vxworks, nevermind

16:44 <IoT-Maker> Maybe i have to disassemble the firmware update process. But thats beyound my abilities. I saw some videos https://www.youtube.com/watch?v=G47tneORZOA. There are 5 videos 6 to 9 hours each. The person could poke around with flash process in firmware file. I can't do that magic. I don't even understand all tricks in this videos.

16:46 <IoT-Maker> bencoh: There firmware image has both, linux kernel and linux stuff, and vxworks. This Drobo NAS runs both systems at the same time. Makes things even harder for a noob like me.

18:18 <IoT-Maker> When i load an image to 0x20000000 it says 13893701 bytes written at address 0x21000000 1362432 bytes written at address 0x21d40060? Why it ignores 0x20000000?