Success with nightly build for TP Link CPE510 v3.8
Howdy all! I successfully configured a newly purchased TP Link CPE510 v3.8 using the nightly build firmware from the following file:
aredn-1476-b452af4-ath79-tplink_cpe510-v3-factory.bin
Thanks so much to all who helped, y'all are amazing!
-Robert K6RGG
And you have the 3.8 version of the device ? Should say it on the sticker or on the box it came in. I have not loaded the newest version yet. There is a means to do the upgrade via the SSH console, and the folks here had directed me to that when going from the stock firmware. You'll have to enable SSH in the stock firmware. But I do not remember having that problem with the fixed firmware. If it fails, You should still be able to recover the device with the original firmware if you get a copy of it. I'll dig out one of these nodes and take a look at upgrading one to the currently nightly and let you know how that goes. I'm sure one of the mods will be along at some point soon also, these folks are very sharp.
OK. Next step is to make sure you know how to recover the Pharos Firmware.
If you know the process we can then try the following
use scp to copy the <nightly>.bin to /tmp on the device
then force it to install with
sysupgrade -v -n -F /tmp/<nightly>.bin
And thank you very much for your kind offer to help. I had another version of this device that I bought a few weeks ago, and it flashed the AREDN firmware on the first try without issue.
Try the nightly build and use something like winscp to copy that file to the /tmp directory on the unit and then the following command should get the upgrade started. <nightly> needs to be replaced with the actual file name. Make sense ? The device will reboot like twice while it upgrades and it will take a few minutes to complete. Just so that you understand, if this fails, it could leave the unit in a state where you will need to tftp boot it with the original firmware, if you aren't comfortable with that, I would hesitate doing it.
I'm able to see the device using WinSCP, but get an error when I try to transfer a file to the tmp directory.
Cannot execute SCP to start transfer. Please make sure that SCP is installed on the server and path to it is included in PATH. You may also try SFTP instead of SCP.
Command failed with return code 1.
What am I missing? Is my PC the server in this scenario? or the CPE510?
I have submitted my PR Request.
Once its approved the device will be available on the ath79 branch for you to download.
aredn-1476-b452af4-ath79-tplink_cpe510-v3-factory.bin
Thanks so much to all who helped, y'all are amazing!
-Robert K6RGG
http://downloads.arednmesh.org/snapshots/trunk/targets/ath79/generic/are...
And you have the 3.8 version of the device ? Should say it on the sticker or on the box it came in. I have not loaded the newest version yet. There is a means to do the upgrade via the SSH console, and the folks here had directed me to that when going from the stock firmware. You'll have to enable SSH in the stock firmware. But I do not remember having that problem with the fixed firmware. If it fails, You should still be able to recover the device with the original firmware if you get a copy of it. I'll dig out one of these nodes and take a look at upgrading one to the currently nightly and let you know how that goes. I'm sure one of the mods will be along at some point soon also, these folks are very sharp.
Model: CPE510(US) Ver: 3.28
In the PHAROS information it says:
https://www.tp-link.com/ca/support/download/cpe510/v3.28/#Firmware
and enabled SSH.
Any tips on flashing the AREDN firmware?
sysupgrade -v -n -F /tmp/<nightly>.bin
Cannot execute SCP to start transfer. Please make sure that SCP is installed on the server and path to it is included in PATH. You may also try SFTP instead of SCP.
Command failed with return code 1.
What am I missing? Is my PC the server in this scenario? or the CPE510?
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#alternate-process
Pages