Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
accessory:add-on_boards:xu4_cloudshell2:firmware_upgrade [2017/10/24 19:09]
neal
accessory:add-on_boards:xu4_cloudshell2:firmware_upgrade [2018/06/12 10:46]
neal [How to upgrade F/W with JSM561 under CloudShell2]
Line 4: Line 4:
  
 ===== Revision history ===== ===== Revision history =====
 +(You can see the current Firmware version using [[accessory:​add-on_boards:​xu4_cloudshell2:​firmware_upgrade#​example_5_show_version_information_of_bridge_chip_firmware|JMS561FwUpdate]] command tool)
  
 +|  #  |  DATE       ​| ​ F/W Base             ​| ​ Release F/W version\\ (Using tool RAID Manager) ​          ​| ​ The F/W release note                                                                        |  Issues ​                                                                                                                                                                                                                                                                                                                                                       |
 +|  0  |  2016.9.19 ​ |  JMS561 Standard F/W  |  <color #​ed1c24>​JMS561b_v8.0.3.7</​color>​\\ (N/A)           ​| ​                                                                                             | <color #​ed1c24>​1</​color>​. SATA device error and disconnect, when requesting \\     the S.M.A.R.T information.(Especially with the option "-l devstat"​ on the second disk)\\ <color #​ed1c24>​2</​color>​. No Raid manager tool for JMS56X controller console version. ​ |
 +|  1  |  2017.6.16 ​ |  JMS561 Standard F/W  |  <color #​ed1c24>​v158.001.000.001</​color>​\\ (V9E.01.00.01) ​ | 1. First release\\ 2. Support USB BOT mode only\\ 3. Support JMS561 RAID AP under Linux O/S  | <color #​ed1c24>​3</​color>​. Not support USB Attached SCSI(UAS) ​                                                                                                                                                                                                                                                                                                  |
 +|  2  |  2017.7.28 ​ |  v158.001.000.001 ​    ​| ​ <color #​ed1c24>​v158.001.000.002</​color>​\\ (V9E.01.00.01) ​ | 1. SMART log display base on WD My Book Duo\\ JMS561 behavior. ​                              | <color #​ed1c24>​3</​color>​. Not support USB Attached SCSI(UAS)\\ <color #​ed1c24>​4</​color>​. smartctl command getting the same serial number and same smart \\      information even if two SATA devices plug on JMS561. ​                                                                                                                                                                                                                                                                                              |
 +|  3  |  2017.8.3 ​  ​| ​ v158.001.000.002 ​    ​| ​ <color #​ed1c24>​v158.001.000.003</​color>​\\ (V9E.01.00.01) ​ | 1. Fix S.M.A.R.T log display issue @ JMS561 SATA Port 1                                      | <color #​ed1c24>​3</​color>​. Not support USB Attached SCSI(UAS)\\ <color #​ed1c24>​4</​color>​. smartctl command getting the same serial number and same smart \\      information even if two SATA devices plug on JMS561.|
 +|  4  |  2017.9.6 ​  ​| ​ v158.001.000.003 ​    ​| ​ <color #​ed1c24>​v158.001.000.004</​color>​\\ (V9E.01.00.04) ​ | 1. Support USB UAS Mode                                                                      | <color #​ed1c24>​5</​color>​. The issue number 1 cannot fix.\\ Jmicron said that there is UAS(USB3.0 host driver) issue of both OS\\ Linux and Windows.\\ <color #​ed1c24>​6</​color>​. The issue number 4 cannot fix. Jmicron said it's H/W limitations(JMS561 is RAID manager chip). ​                                                                                |
  
-|  #  |  DATE       ​| ​ F/W Base             ​| ​ Release F/W version ​                     |  The F/W release note                                                                        |  Issues ​                                                                                                                                                                                                                                                                                                                                                       | +===== How to upgrade F/W with JSM561 ​under Windows=====
-|  0  |  2016.9.19 ​ |  JMS561 Standard F/W  |  <color #​ed1c24>​JMS561b_v8.0.3.7</​color> ​ |                                                                                              | <color #​ed1c24>​1</​color>​. SATA device error and disconnect, when requesting \\     the S.M.A.R.T information.\\ <color #​ed1c24>​2</​color>​. No Raid manager tool for JMS56X controller console version.\\ <color #​ed1c24>​3</​color>​. smartctl command getting the same serial number and same smart \\      information even if two SATA devices plug on JMS561. ​ | +
-|  1  |  2017.6.16 ​ |  JMS561 Standard F/W  |  <color #​ed1c24>​v158.001.000.001</​color> ​ | 1. First release\\ 2. Support USB BOT mode only\\ 3. Support JMS561 RAID AP under Linux O/S  | <color #​ed1c24>​4</​color>​. Not support USB Attached SCSI(UAS) ​                                                                                                                                                                                                                                                                                                  | +
-|  2  |  2017.7.28 ​ |  v158.001.000.001 ​    ​| ​ <color #​ed1c24>​v158.001.000.002</​color> ​ | 1. SMART log display base on WD My Book Duo\\ JMS561 behavior. ​                              | <color #​ed1c24>​4</​color>​. Not support USB Attached SCSI(UAS) ​                                                                                                                                                                                                                                                                                                  | +
-|  3  |  2017.8.3 ​  ​| ​ v158.001.000.002 ​    ​| ​ <color #​ed1c24>​v158.001.000.003</​color> ​ | 1. Fix S.M.A.R.T log display issue @ JMS561 SATA Port 1                                      | <color #​ed1c24>​4</​color>​. Not support USB Attached SCSI(UAS) ​                                                                                                                                                                                                                                                                                                  | +
-|  4  |  2017.9.6 ​  ​| ​ v158.001.000.003 ​    ​| ​ <color #​ed1c24>​v158.001.000.004</​color> ​ | 1. Support USB UAS Mode                                                                      | <color #​ed1c24>​5</​color>​. The issue number 1 cannot fix.\\ Jmicron said that there is UAS(USB3.0 host driver) issue of both OS\\ Linux and Windows.\\ <color #​ed1c24>​6</​color>​. The issue number 3 cannot fix. Jmicron said it's H/W limitations. ​                                                                                                             | +
- +
-===== How to upgrade F/W with JSM561 =====+
  
 I quoted written by lsc117 from odroid forum. And modified it slightly.\\ I quoted written by lsc117 from odroid forum. And modified it slightly.\\
Line 19: Line 19:
 but, We are going to get it Linux version(ARM platform) from Jmicron.\\ but, We are going to get it Linux version(ARM platform) from Jmicron.\\
  
- <​color #​ed1c24>​**0**</​color>​. Pull out the 40pin header ​where connected between XU4 and Cloudshell2 board.\\+ <​color #​ed1c24>​**0**</​color>​. Pull out the 30pin ribbon cable where connected between XU4 and Cloudshell2 board.\\
 It cut the power on XU4.\\ It cut the power on XU4.\\
  
Line 27: Line 27:
  
  <​color #​ed1c24>​**3**</​color>​. Connect your CloudShell2 to a Windows PC via USB cables ( a longer micro USB 2.0 could be fine like this picture)\\  <​color #​ed1c24>​**3**</​color>​. Connect your CloudShell2 to a Windows PC via USB cables ( a longer micro USB 2.0 could be fine like this picture)\\
-{{:internal:playground:cloudshell2_f:​writing_serial.jpg?​600|}}\\+ {{:accessory:add-on_boards:xu4_cloudshell2:​writing_serial.jpg?​600|}} \\ 
  
  <​color #​ed1c24>​**4**</​color>​. Download the writing utility for windows and extract it.\\  <​color #​ed1c24>​**4**</​color>​. Download the writing utility for windows and extract it.\\
Line 33: Line 34:
  
  <​color #​ed1c24>​**5**</​color>​. Download JSM561_FWs.zip into the same utility directory and extract it.\\  <​color #​ed1c24>​**5**</​color>​. Download JSM561_FWs.zip into the same utility directory and extract it.\\
-{{ :internal:playground:cloudshell2_f:​jsm561_fws.zip |}}+{{ :accessory:add-on_boards:xu4_cloudshell2:​jsm561_fws.zip |}}
  
  <​color #​ed1c24>​**6**</​color>​. Run JMMassProd2_v1_16_14_1.exe file.\\  <​color #​ed1c24>​**6**</​color>​. Run JMMassProd2_v1_16_14_1.exe file.\\
  
  <​color #​ed1c24>​**7**</​color>​. Load the Cloudshell2.ini file.\\  <​color #​ed1c24>​**7**</​color>​. Load the Cloudshell2.ini file.\\
- {{:internal:playground:cloudshell2_f:​load_ini.png?​600|}}\\+ {{:accessory:add-on_boards:xu4_cloudshell2:​load_ini.png?​600|}} \\ 
 + 
 <WRAP round important 40%> ​ <WRAP round important 40%> ​
 If you see Error message "​Unable to find the test file : test.bin",​\\ You just ignore it.\\ If you see Error message "​Unable to find the test file : test.bin",​\\ You just ignore it.\\
Line 44: Line 46:
  
  <​color #​ed1c24>​**8**</​color>​. Check RD Version with a password.(<​color #​ed1c24>​password : jmicron</​color>​)\\  <​color #​ed1c24>​**8**</​color>​. Check RD Version with a password.(<​color #​ed1c24>​password : jmicron</​color>​)\\
-{{:internal:playground:cloudshell2_f:​check_rdversion.png?​600|}}\\+{{:accessory:add-on_boards:xu4_cloudshell2:​check_rdversion.png?​600|}} \\
  
  <​color #​ed1c24>​**9**</​color>​. Check "​Firmware Update"​ and Click "Load F/W file" and then select f/w .bin file you want.\\  <​color #​ed1c24>​**9**</​color>​. Check "​Firmware Update"​ and Click "Load F/W file" and then select f/w .bin file you want.\\
Line 53: Line 55:
 </fs> </fs>
 </​WRAP>​ </​WRAP>​
-{{:internal:playground:cloudshell2_f:​load_fw_file_cloudshell2.png?​600|}}+{{:accessory:add-on_boards:xu4_cloudshell2:​load_fw_file_cloudshell2.png?​600|}}
  
  <​color #​ed1c24>​**10**</​color>​. Push Start button.\\  <​color #​ed1c24>​**10**</​color>​. Push Start button.\\
  You can see the progress and then "​Pass"​ displayed in a few seconds.\\  You can see the progress and then "​Pass"​ displayed in a few seconds.\\
  If your CloudShell2 does not show, then you should remove the USB cable to Host PC and try again.\\  If your CloudShell2 does not show, then you should remove the USB cable to Host PC and try again.\\
-{{:internal:playground:cloudshell2_f:​start.png?​600|}}\\ +{{:accessory:add-on_boards:xu4_cloudshell2:​start.png?​600|}} \\ 
-{{:internal:playground:cloudshell2_f:​cloudshell2_fw_done.png?​600|}}+{{:accessory:add-on_boards:xu4_cloudshell2:​cloudshell2_fw_done.png?​600|}} 
 + 
 +===== How to upgrade F/W with JSM561 under CloudShell2 ===== 
 +<WRAP round important 40%> 
 +<fs large> 
 +System power ON and OFF required to apply!!!\\ 
 +After F/W upgrade, you have to system off safely and pull out power plug your CloudShell2.\\ 
 +And then connect it(Power on) again. 
 +</​fs>​ 
 +</​WRAP>​ 
 +=== Parameter definition === 
 +-b    – Backup file \\ 
 +-d    – Device path \\ 
 +-f    – Firmware file \\ 
 +-nNV    – Update without NVRAM. This parameter priority over than “-t” \\ 
 +-t    – Auto spin-down timer. (Unit: minute) \\ 
 +-v    – Show the software version or the bridge version\\ 
 + 
 +=== How to use === 
 +Download JMS561 F/W updater(JMS561FwUpdate) and upload it to your CloudShell2.\\ 
 +{{ :​accessory:​add-on_boards:​xu4_cloudshell2:​jms561_fw_updater_onxu4.tgz |}} \\ 
 +<color #​ed1c24>​Note:​ Please make sure that the device path is correct.</​color>​ 
 + 
 +== Example 0. After upgrading the firmware this procedure must be followed. == 
 +<code (bash)>​ 
 +Safely shutdown the device either through the GUI or by typing "sudo shutdown"​ in an ssh terminal. 
 +Pull the power plug then wait two seconds. 
 +Plug the device back in. When the device boots it will be using the updated firmware. 
 +</​code>​ 
 + 
 +== Example 1. shows version information of software. == 
 +<code (bash)>​ 
 +root@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -v 
 +JMicron Firmware Update Tool v0.0.0.1 
 +Copyright (C) 2017 JMicron Corp. 
 + 
 +root@odroidxu4:​~/​JMS561#​  
 +</​code>​ 
 + 
 +== Example 2. Update device. == 
 +<color #​ed1c24>​Note:​ This step needs root permission.</​color>​ 
 +<code (bash)>​ 
 +root@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -d /dev/sda -f ./​jms561_Hardkernel_v158.001.000.004.bin -b ./​backup.bin 
 +Update Firmware file name: ./​jms561_Hardkernel_v158.001.000.004.bin 
 +Backup Firmware file name: ./​backup.bin 
 +Backup the ROM code sucessfully. 
 +Programming & Compare Success!! 
 + 
 +root@odroidxu4:​~/​JMS561#​  
 +</​code>​ 
 + 
 +== Example 3. Update device without NVRAM  == 
 +This feature does not support update from internal code, but it still finishes the update and show the CAUTION. (The  
 +NVRAM will use a default setting.)\\ 
 +<color #​ed1c24>​Note:​ This step needs root permission.</​color>​ 
 +<​code(bash)>​ 
 +oot@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -d /dev/sda -f ./​jms561_Hardkernel_v158.001.000.004.bin -b ./​backup.bin -nNV 
 +Update Firmware file name: ./​jms561_Hardkernel_v158.001.000.004.bin 
 +Backup Firmware file name: ./​backup.bin 
 +CAUTION: Update firmware without NVRAM. 
 +Backup the ROM code sucessfully. 
 +Programming & Compare Success!! 
 + 
 +root@odroidxu4:​~/​JMS561#​ 
 +</​code>​ 
 + 
 +==  Example 4 - Setting spin-down timer  == 
 +The program has two ways to change spin-down timer, \\ 
 +1.  Update device firmware with spin-down timer. \\ 
 +2.  Only update spin-down timer. \\ 
 +  
 +Please note that the parameter “-t” can’t work with “-nNV”. \\ 
 +Spin-down timer is disabled when the parameter “-t” is set to 0(zero). \\ 
 +<WRAP round important 40%> 
 +Auto Spin-Down time parameter 1 and 2 (1 and 2 minute) is not working. 
 +The minimum is default time 3 (3 minute) 
 +</​WRAP>​ 
 +<color #​ed1c24>​Note. This step need root permission. </​color>​ 
 + 
 +1. Update a device firmware with spin-down timer. 
 +<code (bash)>​ 
 +root@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -d /dev/sda -f ./​jms561_Hardkernel_v158.001.000.004.bin -b ./​backup.bin -t 5 
 +Update Firmware file name: ./​jms561_Hardkernel_v158.001.000.004.bin 
 +Backup Firmware file name: ./​backup.bin 
 +Auto spin-down timer: 5 min. 
 +Backup the ROM code sucessfully. 
 +Programming & Compare Success!! 
 + 
 +root@odroidxu4:​~/​JMS561#​  
 +</​code>​ 
 +2. Only update spin-down timer. 
 +<code (bash)>​ 
 +root@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -d /dev/sda -t 5 
 +Auto spin-down timer: 5 min. 
 +Update auto spin-down timer pass. 
 + 
 +root@odroidxu4:​~/​JMS561#​  
 +</​code>​ 
 + 
 +==  Example 5. Show version information of bridge chip firmware == 
 +<color #​ed1c24>​Note. This step need root permission. </​color>​ 
 +<code (bash)>​ 
 +root@odroidxu4:​~/​JMS561#​ ./​JMS561FwUpdate -d /dev/sda -v 
 +Bridge Firmware Version: v158.1.0.4 
 + 
 +root@odroidxu4:​~/​JMS561#​ 
 +</​code>​
  
 ===== Run script ===== ===== Run script =====
Line 68: Line 176:
 Furthermore,​ They didn't move fast as we thought.\\ Furthermore,​ They didn't move fast as we thought.\\
 That is why we have decided to make this script.\\ That is why we have decided to make this script.\\
 +Simply, this script eliminates "-l scttemp -l scterc"​ on smartctl option in the OMV.
  
 <WRAP round important 60%> <WRAP round important 60%>
Line 74: Line 183:
 You have to run this script. You have to run this script.
 It will change smart command option to prevent system halt.\\ It will change smart command option to prevent system halt.\\
 +JMS561 cannot pass-through the option "-l scttemp -l scterc"​ with smartctl command.\\
 If you want to see JSM561 f/w version, you should use tool JMMassProd2_v1_16_14_1.exe under Windows.\\ If you want to see JSM561 f/w version, you should use tool JMMassProd2_v1_16_14_1.exe under Windows.\\
 Or use raid manager(raidmgr_static) console version under CloudShell2 if you have JSM561 f/w is higher than JMS561b_v8.0.3.7.\\ Or use raid manager(raidmgr_static) console version under CloudShell2 if you have JSM561 f/w is higher than JMS561b_v8.0.3.7.\\
 +Add one thing to check current f/w version under CloudShell2 is that JMS561FwUpdate utility.\\
 +(Refer Example 5. Show version information of bridge chip firmware). \\
 </fs> </fs>
 </​WRAP>​ </​WRAP>​
  
 <color #​ed1c24>​**1**</​color>​. Download this chOpSmartinfo.zip file and extract it.\\ <color #​ed1c24>​**1**</​color>​. Download this chOpSmartinfo.zip file and extract it.\\
-{{ :internal:playground:cloudshell2_f:​chopsmartinfo.zip |}}+{{ :accessory:add-on_boards:xu4_cloudshell2:​chopsmartinfo.zip |}}
  
 <color #​ed1c24>​**2**</​color>​. Upload it to your CloudShell2 and run\\ <color #​ed1c24>​**2**</​color>​. Upload it to your CloudShell2 and run\\
Line 94: Line 206:
 It works when JM561 F/W version is higher than JMS561b_v8.0.3.7.\\ It works when JM561 F/W version is higher than JMS561b_v8.0.3.7.\\
 User Guide for Raid manager included.\\ User Guide for Raid manager included.\\
-{{ :internal:playground:cloudshell2_f:​raidmgr_static_cloudshell2.zip |}}+{{ :accessory:add-on_boards:xu4_cloudshell2:​raidmgr_static_cloudshell2.zip |}}
  
 <color #​ed1c24>​**1**</​color>​. Download this raidmgr_static_cloudShell2.zip and extract it.\\ <color #​ed1c24>​**1**</​color>​. Download this raidmgr_static_cloudShell2.zip and extract it.\\