NMT:DTS: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Flashing a A-110 firmware on A-100 does fail pretty early on. | Flashing a A-110 firmware on A-100 does fail pretty early on. | ||
1) make A100 think its A110. Will it work? Does it check things too deep? (cpukeys etc) | 1) make A100 think its A110. Will it work? Does it check things too deep? (cpukeys etc) | ||
Might not be possible, but if it would work, it would make everything complete. | |||
2) pull out ucode from A110, and add to A100 firmware. Not too hard, but tedious. Have all keys, and CRC code already. | 2) pull out ucode from A110, and add to A100 firmware. Not too hard, but tedious. Have all keys, and CRC code already. | ||
Apart from ucode, other parts of the software might check for model number to enable/disable 2ch mix-down. So we might have to do partial 1) anyway. | |||
3) pull out ucode and attempt to get it to initialise after A100 has booted up. | 3) pull out ucode and attempt to get it to initialise after A100 has booted up. | ||
Unlikely replacing ucode after boot will work, and may still need part of 1) to work. | |||
Revision as of 06:00, 2 December 2008
Flashing a A-110 firmware on A-100 does fail pretty early on.
1) make A100 think its A110. Will it work? Does it check things too deep? (cpukeys etc)
Might not be possible, but if it would work, it would make everything complete.
2) pull out ucode from A110, and add to A100 firmware. Not too hard, but tedious. Have all keys, and CRC code already. Apart from ucode, other parts of the software might check for model number to enable/disable 2ch mix-down. So we might have to do partial 1) anyway.
3) pull out ucode and attempt to get it to initialise after A100 has booted up. Unlikely replacing ucode after boot will work, and may still need part of 1) to work.