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/11/13 18:12]
neal [Run script]
accessory:add-on_boards:xu4_cloudshell2:firmware_upgrade [2018/06/12 10:46] (current)
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 62: Line 62:
 {{:​accessory:​add-on_boards:​xu4_cloudshell2:​start.png?​600|}} \\ {{:​accessory:​add-on_boards:​xu4_cloudshell2:​start.png?​600|}} \\
 {{:​accessory:​add-on_boards:​xu4_cloudshell2:​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 80: Line 186:
 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>​