vsz fw 3.6.2 to standalone FW - problems flashing (r500) - (or what is proper process?)

  • 1
  • Question
  • Updated 6 days ago
  • Answered
  • (Edited)
I thought i had done this path before (ie i have a r500 with vsz FW 3.6.2.x  and trying to flash it to standalone FW , ie 110.x),  but maybe this is my first time going this direction.

Im having issue getting this done (and maybe its bc of the change ~ vsz 3.5 to signed FW?).

Of course in the vSZ AP FW's gui there is no option to change or upload any FW (assuming you have enabeled http/s via ssh on the AP),  so i decided to try to flash its FW via SSH w FTP:

However after a reboot, the AP still comes back up with 3.6.2  (have also tried pressing button 7s to factory defaults, and trying again, same result).

Any ideas?  Or what is the proper process to flash a AP with vSZ FW to Standalone FW?


here are the logs from the flash process via ssh (which is the only way i can see is possible to flash it), note: after the reboot, the ap still has the same vsz FW (not standalone 110.x), and both FW banks on the AP are the vsz FW, 3.6.2.x):
rkscli: fw set port 21
rkscli: fw set control r500_110_cntrl.rcks OK rkscli: fw force-update fw: Updating rcks_wlan.main ... v54_fw_update: download section=rcks_fw.main image=Image1 ctl_file=zf7372_104_cntrl.rcks (/writable/fw/main.cntl) flash id is 0x10220 imghdr.{hdr_len=160, bin_len=10970972} fw_flash_read_open: open((null),) failed rks_flash_read_open(1) failed tail_offset 10968928 bin_len 10970972 sign 1. fwcheck is 2. net_get_flash, Upgrading from Fully Signed Image(FSI) to Intermediate Signed Image(ISI) image. Firmware size mentioned in control file(10971132) _erase_flash: offset=0x0 count=42 Erase Total 42 Units Performing Flash Erase of length 262144 at offset 0xa40000 done [====================================================================================================] 100 + read_size 8192; rc=2044 net_get_flash: Receive last block buf 2044 net_get_flash: hdr_fsize=10969088, real_fsize=10969088 net_buf 0x7ffe3914 Reading Image TAIL:- TLV No-1.TLV INFO Number of TLVS in Tail is 2. Size of Tail is 2044. len 9 tail_len = 9 2. SIGNATURE OBTAINED SUCCESSFULLY len 259 tail_len = 268 cert len 1773 pass 3. CERTICATE OBTAINED SUCCESSFULLY len 1776 tail_len = 2044 1444: rc1 2044 tail_len 2044 MD5 Checksum successful!!!!!!!!! Checking Image hash:- 1. Obtaining public key from Certificate. Executing openssl x509 -in /tmp/in_cert.pem -pubkey -noout >/tmp/pubkey.pem line: Certificate will not expire Certificate validity verified. line: /tmp/in_cert.pem: OK 2. Public key verified. 3. Decrypting the Image signature. Executing openssl rsautl -verify -pubin -inkey /tmp/pubkey.pem -in /tmp/signsure.bin -out /tmp/ext_sha256. 4. Comparing the signatures:- IMAGE TAIL SHA256 : 0a359971c5e62baa9e82a6aac681e922fca8a3ed6b8efb45b35333292781bd45 CALC SHA256 : 0a359971c5e62baa9e82a6aac681e922fca8a3ed6b8efb45b35333292781bd45 HASH CHECK PASSED. AIS cleanup : Removing /tmp/ext_sha256... AIS cleanup : Removing /tmp/in_cert.pem... AIS cleanup : Removing /tmp/signsure.bin... AIS cleanup : Removing /tmp/pubkey.pem... AIS cleanup : Completed bdSave: sizeof(bd)=0x7c, sizeof(rbd)=0xd0 caching flash data from /dev/mtd3 [ 0x00000000 - 0x00010000 ] updating flash data [0x00008000 - 0x000080d0] from [0x7ffea158 - 0x7ffea228] _erase_flash: offset=0x0 count=1 Erase Total 1 Units Performing Flash Erase of length 262144 at offset 0x0 done caching flash data from /dev/mtd3 [ 0x00000000 - 0x00010000 ] verifying flash data [0x00008000 - 0x000080d0] from [0x7ffea158 - 0x7ffea228] **fw(1726) : Completed rkscli: reboot OK rkscli: exit Quit: OK Connection to closed.
Photo of Stephen Hall

Stephen Hall

  • 29 Posts
  • 2 Reply Likes

Posted 6 days ago

  • 1
Photo of Abilash PR

Abilash PR

  • 3 Posts
  • 2 Reply Likes
Hi Stephen,

A Factory reset of the AP should enable you to upgrade the AP's firmware via http/https to your desired version even on vSZ firmware.

The AP's standalone firmware ends with .bl7 please use the below commands and tftp server to upgrade the AP.
fw set host <tftp server's IP address> 
fw set control  rcks_fw.bl7 <110.x version firmware>
fw set proto tftp 
fw update
The below Procedure would require Support's assistance and which should not consume more than 5 mins wait time, I have used it most of the time to do a quick test.

Request them to generate shell key for your AP and run the below command in shell, after running this command please relogin/refresh AP's GUI and should find update option.
rm -f /tmp/wsgclient/isManaging
The above command would enable you to upgrade the Firmware via http/https,  and please use 110.x firmware, using any other version gives you error once it is on 110.x firmware then you can update the AP to older versions.

To verify if your update has been successful or not please run below command.
fw show all

Hope it helps.

Abilash PR.


Photo of Michael Brado

Michael Brado, Official Rep

  • 2729 Posts
  • 382 Reply Likes
Or, don't involve Support and wait for a "shell key"...!  =:^O  Abilash, you've been doing it the hard way.

Just Factory Default the AP, and it will use IP and allow login with uid/pw of super/sp-admin. WebUI should work, your Status::Device page will show scg xxx Software Version, but go to Maintenance::Upgrade and Upgrade Method 'Local' should allow you to point to the 110.0 image for your model AP you downloaded in advance (hint).
Photo of Jonathon Lorek

Jonathon Lorek

  • 1 Post
  • 0 Reply Likes
If the upgrade option still doesn't appear after factory defaulting remove the AP from reaching the controller (Poe injector works), and:

1. factory reset - wait until full bootup before resetting
2. ssh into the AP with super/sp-admin
3. input "set scg disable"
4. input "set https enable"
5. navigate to the ap web interface via https and you should see the "upgrade option" now
6. Install the standalone code bl7 file locally.

- Jonathon