[OpenWrt-Devel] [PATCH v2 2/2] ipq40xx: add support for AVM FRITZ!Repeater 3000

[David Bauer]

Hello Christian,

On 10.03.19 20:27, Christian Lamparter wrote:
> On Saturday, March 9, 2019 12:20:54 AM CET David Bauer wrote:
>> Hardware
>> --------
>> CPU:   Qualcomm IPQ4019
>> RAM:   256M (NANYA NT5CC128M16JR-EK)
>> FLASH: 128M NAND (Macronix MX30LF1G18AC-XKI)
>> ETH:   Qualcomm QCA8072
>> WiFi2: IPQ4019 2T2R 2SS b/g/n
>> WiFi5: IPQ4019 2T2R 2SS n/ac
>> WiFi5: QCA9984 4T4R 4SS n/ac
>> LED:    - Connect green/blue/red
>>         - Power green
>> BTN:   WPS/Connect
>> UART:  115200n8 3.3V
>>        VCC - RX - TX - GND (Square is VCC)
>>
>> Installation
>> ------------
>> 1. Grab the uboot for the Device from the 'u-boot-fritz3000'
>>    subdirectory. Place it in the same directory as the 'eva_ramboot.py'
>>    script. It is located in the 'scripts/flashing' subdirectory of the
>>    OpenWRT tree.
>>
>> 2. Assign yourself the IP address 192.168.178.10/24. Connect your
>>    Computer to one of the boxes LAN ports.
>>
>> 3. Connect Power to the Box. As soon as the LAN port of your computer
>>    shows link, load the U-Boot to the box using following command.
>>
>>    > ./eva_ramboot.py --offset 0x85000000 192.168.178.1 uboot-fritz3000.bin
>>
>> 4. The U-Boot will now start. Now assign yourself the IP address
>>    192.168.1.70/24. Copy the OpenWRT initramfs (!) image to a TFTP
>>    server root directory and rename it to 'FRITZ3000.bin'.
>>
>> 5. The Box will now boot OpenWRT from RAM. This can take up to two
>>    minutes.
>>
>> 6. Copy the U-Boot and the OpenWRT sysupgrade (!) image to the Box using
>>    scp. SSH into the Box and first write the Bootloader to both previous
>>    kernel partitions.
>>
>>    > mtd write /path/to/uboot-fritz3000.bin uboot0
>>    > mtd write /path/to/uboot-fritz3000.bin uboot1
>>
>> 7. Remove the AVM filesystem partitions to make room for our kernel +
>>    rootfs + overlayfs.
>>
>>    > ubirmvol /dev/ubi0 --name=avm_filesys_0
>>    > ubirmvol /dev/ubi0 --name=avm_filesys_1
>>
>> 8. Flash OpenWRT peristently using sysupgrade.
>>
>>    > sysupgrade -n /path/to/openwrt-sysupgrade.bin
>>
>> Signed-off-by: David Bauer <mail at david-bauer.net>
>> ---
>> diff --git a/target/linux/ipq40xx/image/Makefile b/target/linux/ipq40xx/image/Makefile
>> index 3a7ecf39eb..49ff71c6bc 100644
>> --- a/target/linux/ipq40xx/image/Makefile
>> +++ b/target/linux/ipq40xx/image/Makefile
>> @@ -130,6 +130,15 @@ define Device/avm_fritzbox-7530
>>  endef
>>  TARGET_DEVICES += avm_fritzbox-7530
>>  
>> +define Device/avm_fritzrepeater-3000
>> +	$(call Device/FitImageLzma)
>> +	DEVICE_DTS := qcom-ipq4019-fritzrepeater-3000
>> +	DEVICE_TITLE := AVM Fritz!Repeater 3000
>> +	DEVICE_PACKAGES := ath10k-firmware-qca9984-ct fritz-caldata ipq-wifi-avm_fritzrepeater-3000
> The fritz-tffs-nand was just added to openwrt. 
> 
> <https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=50717510e7e556cbc9ef05887900a7dc93a57793>
> 
> Should I add it in place? (And for the 7530 as well?)

I will submit a follow-up patch regarding tis topic as it was merged
without this issue addressed. I have already prepared a patch for this,
but will test it tomorrow on all 3 affected devices (7530, 3000 and 7412).

Best wishes
David

> 
> Cheers,
> Christian
> 
> 
> 

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel