Re: Preparing commit description for "ramips: disable default build for HooToo HT-TM02"
Hi, On 12/14/20 5:32 PM, Adrian Schmutzler wrote: > Sorry, I don't understand what this is about. > > Do you want to disable that device by default? Then just put DEFAULT := n > into the device definition. > > Do you want to improve the support? Then you might need to rephrase the > "question". > > Best > > Adrian > >> -Original Message- >> From: Szabolcs Hubai [mailto:szab...@gmail.com] >> Sent: Dienstag, 8. Dezember 2020 01:37 >> To: openwrt-devel@lists.openwrt.org >> Cc: Russell Morris ; Adrian Schmutzler >> ; David Bauer >> Subject: Re: Preparing commit description for "ramips: disable default build >> for HooToo HT-TM02" >> Thank you Adrian for replying to my confusing mail. Yes, I would like to introduce that 'DEFAULT := n' line in the device definition. As you wrote already, the change is easy, it's a oneliner. I have problems with the commit description, as I can't write simply "This device has a 1.5M kernel size limit during boot and is unbootable since x.", like RP-WD02 disabling commit. [0] I can't write, because it's not true: as I wrote in my previous mail, one could flash and boot successfully the latest version of master through serial. Maybe I should try my luck and send this disabling patch. On the long run, I would like improve support, but it won't be as straightforward as it was in mt7620. But that's for another thread. [0]: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=2dda301d40ec0937f4de1bcec307bbc8adb66958 -- Szabolcs ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: Preparing commit description for "ramips: disable default build for HooToo HT-TM02"
Sorry, I don't understand what this is about.
Do you want to disable that device by default? Then just put DEFAULT := n into
the device definition.
Do you want to improve the support? Then you might need to rephrase the
"question".
Best
Adrian
> -Original Message-
> From: Szabolcs Hubai [mailto:szab...@gmail.com]
> Sent: Dienstag, 8. Dezember 2020 01:37
> To: openwrt-devel@lists.openwrt.org
> Cc: Russell Morris ; Adrian Schmutzler
> ; David Bauer
> Subject: Re: Preparing commit description for "ramips: disable default build
> for HooToo HT-TM02"
>
> On 12/8/20 12:08 AM, Szabolcs Hubai wrote:
> > Hi,
> >
> >
> > I planned to refresh the support of a rt305x SunValley Filehub device:
> > HooToo HT-TM02.
> >
> > I wanted to follow Adrian's and Russel's work for HooToo HT-TM05 and
> > RAVPower RP-WD03 in mt7620 [0].
> >
> >
> > I toought disabling the image generation would be easy, as binwalk
> > showed an oversized kernel: "image size: 1624829 bytes", so it won't
> > boot anyway.
> >
> > DECIMAL HEXADECIMAL DESCRIPTION
> >
> > 0 0x0 uImage header, header size: 64 bytes,
> > header CRC: 0xCB63E9C7, created: 2020-12-06 08:18:07, image size:
> > 1624829 bytes, Data Address: 0x8000, Entry Point: 0x8000, data
> > CRC: 0x10379393, OS: Linux, CPU: MIPS, image type: OS Kernel Image,
> > compression type: lzma, image name: "MIPS OpenWrt Linux-5.4.81"
> > 640x40LZMA compressed data, properties: 0x6D,
> > dictionary size: 8388608 bytes, uncompressed size: 5182719 bytes
> > 5493110x861BF Cisco IOS microcode, for ""
> >
> >
> > But I was unable to verify this because of the following:
> > - wingspinner's uboot [1],[2],[3] reads successfully the whole kernel,
> > but throws "LZMA ERROR 1 - must RESET board to recover" - which is
> > maybe fixable by $(Device/uimage-lzma-loader)
> > - original u-boot loads and boots nicely the oversized kernel
>
> To be correct:
> - original u-boot is able to boot the oversized kernel only when it was
> flashed
> through serial access ("IOVST MAIN MENU" -> "U SPIFlash Upgrade")
> - original u-boot throws "Bad Data CRC" when the oversized kernel is flashed
> through reset button TFTP recovery (10.10.10.254 + "kernel").
>
>
> Cheers,
> Szabolcs
>
>
> >
> >
> > And all compatible rt305x devices (HT-TM02, HT-TM01, RP-WD02 and
> maybe
> > RP-WD01) uses wingspinner's image, as it is installable through the
> > OEM web interface. And it comes with he's custom uboot.
> >
> >
> > What should I write in the commit description now?
> >
> >
> > My plans on refreshing have bad times too as the OKLI Loader is unable
> > to find the "OKLI" magic as the device doesn't map the flash to any
> > memory address.
> >
> > While David ported official U-Boot to ramips target already with the
> > RAVPower RP-WD009 support, I'm little bit afraid of my success porting
> > it to rt305x as U-Boot doesn't have "rt5350.dtsi" to start with.
> >
> >
> >
> > May I ask for help not just for commit description but for creating a
> > second stage loader for ramips/rt305x too?
> >
> >
> >
> > Thanks,
> > Szabolcs
> >
> >
> >
> > [0]:
> >
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=log;h=c4110a524e9a026
> > cf570b6dadf325c037b7527d0
> > [1]: https://openwrt.org/toh/hootoo/tripmate-nano#supported_versions
> > [2]: https://forum.archive.openwrt.org/viewtopic.php?id=53014
> > [3]:
> > https://github.com/wingspinner/HooToo-Tripmate-HT-TM02-
> OpenWRT/tree/ma
> > ster/uboot
> >
openpgp-digital-signature.asc
Description: PGP signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Preparing commit description for "ramips: disable default build for HooToo HT-TM02"
On 12/8/20 12:08 AM, Szabolcs Hubai wrote:
> Hi,
>
>
> I planned to refresh the support of a rt305x SunValley Filehub device:
> HooToo HT-TM02.
>
> I wanted to follow Adrian's and Russel's work for HooToo HT-TM05 and
> RAVPower RP-WD03 in mt7620 [0].
>
>
> I toought disabling the image generation would be easy,
> as binwalk showed an oversized kernel: "image size: 1624829 bytes",
> so it won't boot anyway.
>
> DECIMAL HEXADECIMAL DESCRIPTION
>
> 0 0x0 uImage header, header size: 64 bytes,
> header CRC: 0xCB63E9C7, created: 2020-12-06 08:18:07, image size:
> 1624829 bytes, Data Address: 0x8000, Entry Point: 0x8000, data
> CRC: 0x10379393, OS: Linux, CPU: MIPS, image type: OS Kernel Image,
> compression type: lzma, image name: "MIPS OpenWrt Linux-5.4.81"
> 640x40LZMA compressed data, properties: 0x6D,
> dictionary size: 8388608 bytes, uncompressed size: 5182719 bytes
> 5493110x861BF Cisco IOS microcode, for ""
>
>
> But I was unable to verify this because of the following:
> - wingspinner's uboot [1],[2],[3] reads successfully the whole kernel,
> but throws "LZMA ERROR 1 - must RESET board to recover" - which is maybe
> fixable by $(Device/uimage-lzma-loader)
> - original u-boot loads and boots nicely the oversized kernel
To be correct:
- original u-boot is able to boot the oversized kernel only when it was
flashed through serial access ("IOVST MAIN MENU" -> "U SPIFlash Upgrade")
- original u-boot throws "Bad Data CRC" when the oversized kernel is
flashed through reset button TFTP recovery (10.10.10.254 + "kernel").
Cheers,
Szabolcs
>
>
> And all compatible rt305x devices (HT-TM02, HT-TM01, RP-WD02 and maybe
> RP-WD01) uses wingspinner's image, as it is installable through the OEM
> web interface. And it comes with he's custom uboot.
>
>
> What should I write in the commit description now?
>
>
> My plans on refreshing have bad times too as the OKLI Loader is unable
> to find the "OKLI" magic as the device doesn't map the flash to any
> memory address.
>
> While David ported official U-Boot to ramips target already with the
> RAVPower RP-WD009 support, I'm little bit afraid of my success
> porting it to rt305x as U-Boot doesn't have "rt5350.dtsi" to start with.
>
>
>
> May I ask for help not just for commit description but for creating
> a second stage loader for ramips/rt305x too?
>
>
>
> Thanks,
> Szabolcs
>
>
>
> [0]:
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=log;h=c4110a524e9a026cf570b6dadf325c037b7527d0
> [1]: https://openwrt.org/toh/hootoo/tripmate-nano#supported_versions
> [2]: https://forum.archive.openwrt.org/viewtopic.php?id=53014
> [3]:
> https://github.com/wingspinner/HooToo-Tripmate-HT-TM02-OpenWRT/tree/master/uboot
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Preparing commit description for "ramips: disable default build for HooToo HT-TM02"
Hi, I planned to refresh the support of a rt305x SunValley Filehub device: HooToo HT-TM02. I wanted to follow Adrian's and Russel's work for HooToo HT-TM05 and RAVPower RP-WD03 in mt7620 [0]. I toought disabling the image generation would be easy, as binwalk showed an oversized kernel: "image size: 1624829 bytes", so it won't boot anyway. DECIMAL HEXADECIMAL DESCRIPTION 0 0x0 uImage header, header size: 64 bytes, header CRC: 0xCB63E9C7, created: 2020-12-06 08:18:07, image size: 1624829 bytes, Data Address: 0x8000, Entry Point: 0x8000, data CRC: 0x10379393, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS OpenWrt Linux-5.4.81" 640x40LZMA compressed data, properties: 0x6D, dictionary size: 8388608 bytes, uncompressed size: 5182719 bytes 5493110x861BF Cisco IOS microcode, for "" But I was unable to verify this because of the following: - wingspinner's uboot [1],[2],[3] reads successfully the whole kernel, but throws "LZMA ERROR 1 - must RESET board to recover" - which is maybe fixable by $(Device/uimage-lzma-loader) - original u-boot loads and boots nicely the oversized kernel And all compatible rt305x devices (HT-TM02, HT-TM01, RP-WD02 and maybe RP-WD01) uses wingspinner's image, as it is installable through the OEM web interface. And it comes with he's custom uboot. What should I write in the commit description now? My plans on refreshing have bad times too as the OKLI Loader is unable to find the "OKLI" magic as the device doesn't map the flash to any memory address. While David ported official U-Boot to ramips target already with the RAVPower RP-WD009 support, I'm little bit afraid of my success porting it to rt305x as U-Boot doesn't have "rt5350.dtsi" to start with. May I ask for help not just for commit description but for creating a second stage loader for ramips/rt305x too? Thanks, Szabolcs [0]: https://git.openwrt.org/?p=openwrt/openwrt.git;a=log;h=c4110a524e9a026cf570b6dadf325c037b7527d0 [1]: https://openwrt.org/toh/hootoo/tripmate-nano#supported_versions [2]: https://forum.archive.openwrt.org/viewtopic.php?id=53014 [3]: https://github.com/wingspinner/HooToo-Tripmate-HT-TM02-OpenWRT/tree/master/uboot ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
