2013/9/9 Rafał Miłecki <zaj...@gmail.com>: > 1) flash [options] source-file [destination-file] > Passing source-file is easy (like 192.168.1.2:/bin/code.bin), but I'm > not sure about destination-file. > >> The destination-device parameter may be a flash device or an EEPROM. If not >> specified, destination-device defaults to flash0, which is typically the >> boot ROM. > > If I don't pass anything as destination-file argument... Is CFE going > to write to the flash at offset 0x0? Overwriting itself? Or is it > going to write to the correct TRX offset? If it's going to use 0x0 by > default, should I pass -offset=value to avoid killing the CFE?
I think I could use "flash0.trx" as a destination-file instead of using "flash0" and hacking it with -offset. What do you think about this: flash -noheader 192.168.1.2:openwrt-brcm47xx-squashfs.trx flash0.trx (Please see attached cfe.show.devices.txt). -- Rafał
CFE> show devices CMD: [show devices] Device Name Description ------------------- --------------------------------------------------------- uart0 NS16550 UART at 0x18000300 flash0.boot ST Serial flash offset 00000000 size 256KB flash0.trx ST Serial flash offset 00040000 size 1KB flash0.os ST Serial flash offset 0004001C size 7872KB flash0.nvram ST Serial flash offset 007F0000 size 64KB flash1.boot ST Serial flash offset 00000000 size 256KB flash1.trx ST Serial flash offset 00040000 size 7872KB flash1.nvram ST Serial flash offset 007F0000 size 64KB flash0 ST Serial flash size 8192KB eth0 Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller *** command status = 0
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel