User Tools

Site Tools


projects:zsun-wifi-card-reader:factory-update

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
projects:zsun-wifi-card-reader:factory-update [2016/01/26 22:39] informaticprojects:zsun-wifi-card-reader:factory-update [2016/02/19 18:22] (current) informatic
Line 1: Line 1:
 ====== Zsun Card Reader Firmware Update Format ====== ====== Zsun Card Reader Firmware Update Format ======
 +
 +**2016/02/19 Note:** This method has been tested multiple times on our devices and worked without problem, however at least three unexpected bricks have been reported! (sounding like failed rootfs flash)
  
 **TL;DR** **TL;DR**
 +  - Insert FAT32-formatted microSD card (128MB is more than enough)
   - Connect to WiFi   - Connect to WiFi
   - http://10.168.168.1:8080/goform/Setcardworkmode?workmode=0   - http://10.168.168.1:8080/goform/Setcardworkmode?workmode=0
-  - Copy ''SD100-update.tar.gz'' (https://hackerspace.pl/~informatic/SD100-openwrt.tar.gz) to ''.update'' on SMB/Windows Share+  - Create ''.update'' directory on Zsun SMB/Windows Share (on Windows call it ''.update.'', don't ask why - it'll work) and copy ''SD100-openwrt.tar.gz'' (https://hackerspace.pl/~informatic/SD100-openwrt.tar.gz) there
   - http://10.168.168.1:8080/goform/upFirmWare   - http://10.168.168.1:8080/goform/upFirmWare
-  - LED keeps blinking even after flashing finishedso just wait for 2 minutes and you should be fine. +  - Wait for long LED flashthen multiple fast flashes now OpenWRT is booting for the first time.
-  Reconnect zsun.+
   - ... PROFIT!   - ... PROFIT!
  
Line 18: Line 20:
 ''/goform/upFirmWare'' reads update tarball from ''.update/'' directory on microSD card. (''/etc/disk/.update'') Sadly that directory is removed on mount by ''/sbin/lbd_mount'', thus it has to be uploaded using SMB/Windows Network Shares. ''/goform/upFirmWare'' handler is at ''.text:0x00405E04'' address in ''/var/webs/webs'' binary. It does multiple checks and then executes ''/etc/ath/update.sh'' which handles all the actual update. After that device is rebooted. ''/goform/upFirmWare'' reads update tarball from ''.update/'' directory on microSD card. (''/etc/disk/.update'') Sadly that directory is removed on mount by ''/sbin/lbd_mount'', thus it has to be uploaded using SMB/Windows Network Shares. ''/goform/upFirmWare'' handler is at ''.text:0x00405E04'' address in ''/var/webs/webs'' binary. It does multiple checks and then executes ''/etc/ath/update.sh'' which handles all the actual update. After that device is rebooted.
  
-Furthermore ''S'' update action executes ''./mtd_write'' after entering ''/etc/disk/.update'' thus we have to bundle that with update package too. After flashing rootfs device will fail to reboot - there is no way to tell if flashing succeeded or not (although - if upFirmWare returns status 2 and zsun keeps blinking its led for some time - it most probably worked)+Furthermore ''S'' update action executes ''./mtd_write'' after entering ''/etc/disk/.update'' thus we have to bundle that with update package too. After flashing rootfs ''/sbin/reboot'' will fail. This is why we have minimal statically linked reboot executable. (''minreboot'')  
 + 
 +What we are basically doing is hijacking ''./mtd_write'' execution and doing our own calls to ''./mtd_write.actual'' (yes, actual ''mtd_write'' binary), and then just running ''/tmp/minreboot'' (copied there at the beginning of update script, since ''/tmp'' stays in ramfs)
  
 Expected update file format is: Expected update file format is:
projects/zsun-wifi-card-reader/factory-update.1453847960.txt.gz · Last modified: 2016/01/26 22:39 by informatic

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki