Online ImageBuilder and Upgrade Server

#104

I was using nlbwmon before wrtbwmon :slightly_smiling_face:

The reason why I use wrtbwmon is that it has realtime bandwith monitoring.
So I can see who is hogging my bandwidth :slight_smile:

#105

thank you i've been looking for this

#106

Have a quick question.. I have created my own custom firmware on the website, but that was weeks ago and since then many packages have been upgraded yet when I try to generate a new firmware with same (but updated) packages it just gives me the same link to my last firmware created. Is there a way to force to create a new firmware with the updated packages? Seems a liitle weird you can only generate one and then wait until it gets deleted? Have I missed something? Thanks in advance.

#107

Hi, please see this issue to understand the problem. I have to optimize the database query, if you have experience with that I'm happy to elaborate.

1 Like
#108

I dont sorry, thanks for clarifying the issue.

#109

I can try to help with the database issue.

#110

Could this tool be used to build a custom image the header values overridden in tp-link.mk?

I'm trying to recover from a bad flash I caused by stopping in mid-process without realizing, and I think I'm running into the issue described here:

https://openwrt.org/toh/tp-link/archer-c5-c7-wdr7500#tftp_recovery_de-bricking

Note: the TFTP flashing process requires that the product hardware id and version in the new image header match those in the existing image in flash, otherwise the new image is rejected, flashing is cancelled and the bootloader proceeds to boot the old image.

While this would be a fine safety feature in another context, it means the recovery process can reject a valid new image if the image in flash is corrupted. Unfortunately, such corruption can easily occur if the flashing process is interrupted: when an image is accepted, the flashing process first erases the whole space, which takes a while, and then writes the new image. If this process is interrupted during the erasure phase, the in flash header will appear as all 0xFF, and further recovery attempts will therefore fail because the header hardware id and version values will no longer match. If this happens, you'll need to try either a serial connection, or building an image with the header values overridden (in tp-link.mk set TPLINK_HWREV and TPLINK_HWID to 0xffffffff ).

Thanks for any help or even pointers in the right direction...

#111

Hi @dsteven53, this is currently not supported and very specific, therefore out of scope for this project. However, if you need help build an image yourself, please send a PM.

#112

Great work. Thanks for taking the time to do it properly, @aparcar :slight_smile:

#113

We are getting this:

"You're not moving forward in queue for a long time, please report this"

#114

Worker was down. Should work again, please check!

1 Like
#115

Worker generates some unusual files and for all of them we are getting this error when doing a sysupgrade:

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

Previously we were able to obtain the usual files:

*-squashfs-factory.bin
*-squashfs-sysupgrade.bin

Device is a TL-WL841ND v8. Anyone else getting similar results?