[Frage] tools/push_firmware works for 7490, but not for 7590. What info am I missing???

[frater]

If I try to push a 7590 firmware I get the message that I need to use a hidden root 'kernel.image' containing both Linux kernel and file system
I have no idea what is meant here.
In the bash script there's a small loop created where the folder

I just created a completely new HyperV virtual machine with Debian 10 and created a new environment with 'git clone https://github.com/Freetz/freetz.git' because I ran into this problem with my old environment and I was afraid it had something to do with old content somehow.
The virtual machine was more than 5 years old and already had a dist-upgrade.
The machine needed to be replaced anyhow.

I went through the bash script and found a little loop that processes the firmware before it can be pushed.
After it has processed the image is tested with hexdump
Apparently it goes wrong because hexdump -n4 "$tmpimg" results in "9112 feed" for a 7590
On a 7490 it indeed gets the wanted "1281 feed".
This itself doesn't help me further to the solution.

Is the code of push_firmware at fault here or do I need to do something else to get myself an image that can be processed?
I deleted the .config before I tested this to minimize the chance that one of the options I chose is the culprit of this.

rm .config
make menuconfig
# in menuconfig select the 7590 fritzbox
make
tools/push_firmware images/7590_07.12-freetz-master-20190813-77e64b8c6-dirty.de_20190814-154617.image

Hint: file seems to be a full firmware image archive in 'tar' format
containing the 'kernel.image'. Now trying to unpack and use that image.


Error: file is not a valid image to be written to mtd1. Please use a
hidden root 'kernel.image' containing both Linux kernel and file system.


make menuconfig
# in menuconfig select the 7490
make
tools/push_firmware images/7490_07.12-freetz-master-20190813-77e64b8c6-dirty.de_20190814-162415.image

Hint: file seems to be a full firmware image archive in 'tar' format
containing the 'kernel.image'. Now trying to unpack and use that image.

ncftp command found.

!!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!!
!!! THERE IS NO WARRANTY AT ALL !!! USE AT YOUR OWN RISK !!!

Are you sure, that you want to flash /tmp/freetzQah directly to mtd1?

proceed (y/n)

 

[NDiIPP]

The Tool push_firmware (in freetz, at freetz-ng this is different) works neither for 7490 nor for the 7590. For newer models uses e.g. eva_to_memory, in freetz to find under ../tools/yf/eva_tools/.

More on this:
/howto-fritz-box-firmware-images-auch-unsignierte-ueber-den-bootloader-installieren-577#p3852

 

[frater]

OK... Thanks.
I was able to successfully flash a 7490 7.12 with tools/push_firmware though....

I don't understand why it is still distributed then...

 

[frater]

I read that thread and it has me confused on how I was able to flash a 7490 with "push_firmware".
Looking at the tables given in that thread, both the 7490 and 7590 are of type "nand"
push_firmware should not work on a 7490 I????)

Anyhow...
It seems I need to run these 2 commands.

tools/yf/eva_tools/image2ram <images/7590_07.12-freetz-master-20190813-77e64b8c6-dirty.en_20190814-150835.image >images/7590_07.12-freetz-master-20190813-77e64b8c6-dirty.en_20190814-150835.image.in-memory

tools/yf/eva_tools/eva_to_memory images/7590_07.12-freetz-master-20190813-77e64b8c6-dirty.en_20190814-150835.image.in-memory 192.168.178.1

I can't test this now.
I just ran this from a remote location, but no Fritzbox is now attached, so this has to wait until tomorrow.

I can remember that "make" created an image.in-memory each time. It now doesn't anymore. How can I turn this on again?

 

[gismotro]

I can remember that "make" created an image.in-memory each time. It now doesn't anymore. How can I turn this on again?

You have to aktivate it in your menu config:
1.)
2.)

 

[frater]

Thanks....
I looked before, but I didn't find it.
Now I did. ;-)

 

[NDiIPP]

I was able to successfully flash a 7490 7.12 with tools/push_firmware though....

Sorry, but I do not believe you because that can not work with push_firmware from freetz on a 7490. This is only possible with the push_firmware from freetz-ng.

I don't understand why it is still distributed then...

For other Models (e.g., 7270, 7390, 4020, 4040, 6490, 6590 and also many older Models) which can be flashed directly.