Bug 24 - Reader 2.4.2 with UOM=255 is treated as up-to-date Reader.
Summary: Reader 2.4.2 with UOM=255 is treated as up-to-date Reader.
Status: VERIFIED WONTFIX
Alias: None
Product: TestProduct
Classification: Unclassified
Component: TestComponent (show other bugs)
Version: unspecified
Hardware: PC Windows
: Highest blocker
Assignee: Brian Roberge
URL:
Depends on:
Blocks:
 
Reported: 2018-07-11 21:50 EDT by Kuanshen An
Modified: 2018-08-10 23:56 EDT (History)
0 users

See Also:

Attachments
log from windows build 643. (2.76 KB, text/plain)
2018-07-11 21:50 EDT, Kuanshen An 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kuanshen An 2018-07-11 21:50:35 EDT 
Created attachment 6 [details]
log from windows build 643.

this is not same as bug9 which is unplugged during upgrade.
this is latest firmware but configured UOM as 255. It for testing FWRS60*.

FWRS60*, If the Reader firmware is up-to-date, the Firmware Update Application shall check if UOM is correctly configured.


repro step.
1. Get a latest Reader and change its UOM to 255 ( $uom,255).
2. Launch FUA.

Actual result:
App treat is as up-to-date Reader. no correction and no checking for incorrect UOM.

Expected result:
according FWRS60, FUA should check if UOM is correctly configured.
Comment 1 Brian Roberge 2018-07-18 13:51:11 EDT 
The FUA will only fix the invalid UOM if the FUA set the UOM to 255.  If it was set manually the FUA does not know the correct UOM.
Comment 2 Kuanshen An 2018-08-10 23:56:20 EDT 
yes. Brian is right on this.