|
2008-05-27
, 10:35
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#2
|
The Following User Says Thank You to Bundyo For This Useful Post: | ||
|
2008-05-27
, 10:56
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#4
|
|
2008-05-27
, 11:02
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#5
|
|
2008-05-28
, 07:53
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#6
|
osso-product-info -s OSSO_VERSION=`cat /etc/osso_software_version` || true
The Following User Says Thank You to qwerty12 For This Useful Post: | ||
|
2008-05-28
, 09:04
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#7
|
wlan-cal is ran at initfs time to set countries, default values etc.
bt-cal sets the default bluetooth address.
Fanoush, do you know if the config partition is checksummed in any way? I don't want to be the owner of a brick that way :/
The Following User Says Thank You to fanoush For This Useful Post: | ||
|
2008-05-28
, 09:12
|
|
Posts: 4,274 |
Thanked: 5,358 times |
Joined on Sep 2007
@ Looking at y'all and sighing
|
#8
|
|
2008-05-28
, 09:13
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#9
|
CAL is where things like the software version and wlan channels are stored.
cal-tool in the initfs can read things that are set (things like whether rd-mode is enabled via flasher etc)
osso-product-info will query cal for information about the software channels, software version.
You can actually modify that bit of CAL on device:
http://i26.tinypic.com/2znv3gx.png
When you flash a FIASCO image, CAL is written to with the new software information (thanks fanoush)
flasher-3.0 writes to CAL to set things like RD Mode and Phoenix (I'm very sure this one accesses CAL)
Nitro queries CAL and craps out if the cal is corrupted. (I've still got the debs )
I'm sure that the "config" partition (/dev/mtd1ro) stores CAL information as I've had RD mode set and dumped my mtd1 and had it show up in N800 emulation (I believe RD mode is CAL thing too)
The CAL software information corrupts very easily. I've only fixed it by reflashing entire bin image. And that is not a fix. I've had it corrupting by flashing a new kernel via flasher-3.0 and by 0xFFFF. In 0xFFFF I saw it corrupting by odd characters appearing.
When CAL is corrupted, your version's in about change to <unknown> and if you run osso-product-info, you will see <cal_read_block> error while reading (something like that) and if your cal is corrupted nitro will not run.
Maybe osso-product-info will fix an <unknown> software version? Haven't tried it.
But I think it would be nice if we could edit the CAL and reflash it (hell, not even that as it doesn't get reflashed). It could mean things like setting RD mode and flags off the device and it probably means a sure fire way to fixing <unknown> and to edit the wlan channels of the device (I believe US N800's have same WLAN chip but channels are locked down - I'm so glad mine is ETSI/EU )
Programs that write to CAL probably are : flasher-3.0, 0xFFFF (not sure on this one) and Phoenix and osso-product-info.
Last edited by qwerty12; 2008-05-27 at 10:34.