I have a German 7590 (firmware_version avm) and I moved to an area which works annex A. So I have to change the f/w to the international one that supports this.
The bootloader is locked so I have to modify the f/w image. I've read several threads and followed the wiki (http://trac.freetz.org/wiki/help/howtos/development/repack_fw) I manage to get a working image (with a modified rc.conf).
The procedure to get a working image is easy to follow but it took me very long time and tries to flash my image to the box.
From the (bad) google translate I'm not able to get how to correctly perform the flash - furthermore I did not understand what I need to do in order to sign my image and thus be able to flash easily a newer version next time.
I must say here that it took me long time to realize that windows 7 powershell does not work. I used windows 10 PS with eva-ftp-client.ps1 to make it happen. With my bad understanding I must have tried 100 times to manage to get something custom into the box.
Now the box runs my firmware. I did it, but I need to know the correct way.
Using "make menuconfig" & fwmod, I get two files: "my7590.image" and "my7590.in-memory". Do I use the PS scripts to load the in-memory file and then flash the image? Or loading only the in-memory will move itself to flash?
In menuconfig -> fwmod options, I've checked "sign image" and entered a password - 8 letters long. This created a file "\etc\avm_firmware_public_key9". Now that the box runs my firmware I checked the etc directory and the file is there (and has a long string of characters).
But when I try to load a newer make (with some other modifications) I get signature error and will not flash. The newer make is signed using the same password.
What I'm doing wrong?
The bootloader is locked so I have to modify the f/w image. I've read several threads and followed the wiki (http://trac.freetz.org/wiki/help/howtos/development/repack_fw) I manage to get a working image (with a modified rc.conf).
The procedure to get a working image is easy to follow but it took me very long time and tries to flash my image to the box.
From the (bad) google translate I'm not able to get how to correctly perform the flash - furthermore I did not understand what I need to do in order to sign my image and thus be able to flash easily a newer version next time.
I must say here that it took me long time to realize that windows 7 powershell does not work. I used windows 10 PS with eva-ftp-client.ps1 to make it happen. With my bad understanding I must have tried 100 times to manage to get something custom into the box.
Now the box runs my firmware. I did it, but I need to know the correct way.
Using "make menuconfig" & fwmod, I get two files: "my7590.image" and "my7590.in-memory". Do I use the PS scripts to load the in-memory file and then flash the image? Or loading only the in-memory will move itself to flash?
In menuconfig -> fwmod options, I've checked "sign image" and entered a password - 8 letters long. This created a file "\etc\avm_firmware_public_key9". Now that the box runs my firmware I checked the etc directory and the file is there (and has a long string of characters).
But when I try to load a newer make (with some other modifications) I get signature error and will not flash. The newer make is signed using the same password.
What I'm doing wrong?