Difference between revisions of "MIB Exception List file"
(Created page with "Purpose == File names and locations == * /tsd/etc/slist/'''signed_exception_list.txt''' * /HBpersistence/FEC/'''Exceptionlist.txt''' * '''prodEL.txt''' == File Content == ==...") |
(→List of supported FSCs) |
||
| Line 40: | Line 40: | ||
fsc2 = "00040100"<br /> | fsc2 = "00040100"<br /> | ||
fsc3...</code> | fsc3...</code> | ||
| + | |||
| + | FEC can be provided as a range of values, for example <code>fsc = "02100000;0210003F"</code>. | ||
=== Signature === | === Signature === | ||
Revision as of 14:58, 20 August 2020
Purpose
Contents
File names and locations
- /tsd/etc/slist/signed_exception_list.txt
- /HBpersistence/FEC/Exceptionlist.txt
- prodEL.txt
File Content
Fazit IDs
There's a mechanism that can secure the file and prohibit for using it in different device than it's intended to.
Example: VVV-074DD.MM.YYZZZZZZZZ
- VVV = vendor or main unit code name
- DD = production day
- MM = production month
- YY = production year
- ZZZZZZZZ = VCRN
There seems to be a workaround mechanism by replacing characters with ?. That way we get ???-?????.??.?????????? which in theory should be accepted as valid by main units with different VCRNs and production dates.
Different main unit versions use different 3-character prefix. [1]
- JTB = MIB1
- BKA = MIB2
- JTH
- AW7
- YJL
- HHA
Boardbook data path
Destination = "/net/mmx/mnt/boardbook"
SigDestination = "/net/mmx/mnt/boardbook/RSDB"
PPOI data path
Destination = "/net/mmx/mnt/navdb/PersonalPOI"
List of supported FSCs
[SupportedFSC]
fsc = "00030000"
fsc2 = "00040100"
fsc3...
FEC can be provided as a range of values, for example fsc = "02100000;0210003F".
Signature
[Signature]
signature1 = ...
Parsing
Process tsd.mibstd2.system.swap checks the file, compares production date, VCRN, signature. If it's all OK, then it passes listed FEC codes ad valid.
