* Alberto Bursi <alberto.bu...@outlook.it> wrote: > > > On 11/03/2016 10:13 AM, Tino Reichardt wrote: > > Most of these Modems have only a very small flash of 2MB or 4MB .. so > > there is no need for lot of stuff. My aim is to have nice DSL modems > > with recent kernel and dsl firmware. pppoe is not really needed, but > > will fit also into that flash, I think. > > > > Default LEDE image (router firmware with switch/router/firewall/wifi) > fits in 4MiB of flash (also with luci webinterface, if it is integrated > at firmware generation time), there are plenty of other supported > devices with 4MiB of flash.
Yes, my device has 4MB. > > > Where should I add my pictures and descriptions of that modem. Should I > > make an extra project page onto my homepage, or is the lede wiki okay > > for that? When okay, I need some sample device page of current lede > > wiki. > > > > For now the lede wiki isn't ready yet for devices, you can open a thread > in the LEDE forum in the development section, and the info will be moved > to the wiki when it is ready. > https://forum.lede-project.org/ I will post there in the evening... > > > Is it important, to have an own working uboot, or should I create some > > kernel/rootfs image first ? What is the correct way? When I brick the > > current vendor uboot, is there a way, to restore it via serial > > interface? > > > > Most LEDE devices don't touch the vendor u-boot (or bootloaders) unless > they really have to, the LEDE firmware you make should mimic the stock > firmware's place on flash so the bootloader will boot it without > complaining. > > The reason is that if you do a mistake and corrupt/damage the uboot, the > device will not boot anymore and recovery will require complex > procedures with (expensive) JTAG tools or desoldering the flash chip and > using another device to re-program it. Yes, I will not touch the loader then... currently this loader is the main problem I have, cause it's not loading my new built kernel 4.4.30 :( This is the error I get: <snip> AMAZON_SE # tftpboot Using AMAZON_SE Switch device TFTP from server 192.168.1.2; our IP address is 192.168.1.1 Filename 'uImage'. Load address: 0x80100000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################## done Bytes transferred = 3145732 (300004 hex) AMAZON_SE # bootm 0x80100000 Checking Images Integrity ... Kernel: OK Rootfs: OK ## Booting image at 80100000 ... Image Name: MIPS LEDE Linux-4.4.30 Created: 2016-11-03 7:34:38 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1358940 Bytes = 1.3 MB Load Address: 80002000 Entry Point: 80002000 Verifying Checksum ... OK Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 561 Decoding error = 1 LZMA ERROR 1 - must RESET board to recover U-Boot 1.1.5-2.0 (Jan 24 2013 - 13:38:46) </snap> The error comes from lzma version 4.40 and seems not related to the lzma dictionary size option -d23 .. -d20 and so on... -> the default Allnet Image uses 8Mib dictionary size also Here is the code which does the warning: https://dev.openwrt.org/browser/trunk/package/uboot-ifxmips/files/lib_generic/LzmaDecode.c?rev=13291 U-Boot Information: http://pastebin.com/fEj7TxDJ Default Kernel Log: http://pastebin.com/1jiDffmG There were also some fixes, which may related to that issue, I don't know currently: http://lists.denx.de/pipermail/u-boot/2013-December/169963.html http://lists.denx.de/pipermail/u-boot/2014-December/197550.html https://www.google.com/#q=lzma+fix+buffer+bound+site:lists.denx.de -- Best regards, Tino _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev