#14745: changeset 34554 breaks crc check on wrtu54g-tm
-----------------------+-----------------------------------
  Reporter:  lorenzen  |      Owner:  developers
      Type:  defect    |     Status:  new
  Priority:  normal    |  Milestone:  Barrier Breaker 14.07
 Component:  packages  |    Version:  Trunk
Resolution:            |   Keywords:  adm8668
-----------------------+-----------------------------------

Comment (by lorenzen):

 I think I have an even better solution.

 Inspired by how they handled a similar problem with the wrt160nl (ticket
 8960) I though I would just try a similar cure here.
 and it works very well, adding just 17 lines and making 105 lines
 redundant in the codebase. and now sysupgrade transfer of config files
 works too.

 Before the  lzma-loader, linux-kernel, squashfs where encapsulated in an
 uImage. which has a crc-check
 The cure is to only encapsulate lzma-loader and linux-kernel in the uImage
 and append squashfs and maybe files saved by sysupgrade to it

 The best part is that we can remove the whole fixing of the crc in
 driver/mtd/maps/adm8668.c since it will never be executed.
 I have successfully installed a new systems both with u-boot
 update_kernel, and sysupgrade.

 Here are the necessary changes to target/linux/adm8668/image/Makefile
 relative to r42162
 I will update the https://dev.openwrt.org/ticket/14745 with full changes
 shortly

 for people wanting to use  fw_printenv/fw_setenv on the uboot environment,
 you need to do:

 $  echo /dev/mtd3 0 0x400 0x2000 >/etc/fw_env.config

 I have put that into my code base under target/linux/adm8668/base-
 files/etc/fw_env.config
 it would be nice if that would be part of the code-base too

 I have uploaded a diff relative to r42162

--
Ticket URL: <https://dev.openwrt.org/ticket/14745#comment:5>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to