| ??? 03/31/05 15:28 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#90755 - LPC900 Config Bytes Responding to: ???'s previous message |
This information is NOT something that KEIL created. It is something that is simply required for the LPC900 devices.
Well, Andy from ESA and I discussed this last night and I now have a different story. UCFG1 does not have a physical address on the part after all. Keil and Philips worked together on the start-up file and agreed to store the configuration data at 0xFFF0 and up in CODE space. This would allow device programmers to grab the configuration data from the HEX file and program it into the device. Aparently, a lot of other companies adopted this scheme and even I was confused as to who originated it. As far as the layout of these bytes, they are identical to the configuration data described in the User Manual for the LPC900 devices. Sorry for the misinformation. Jon |
| Topic | Author | Date |
| Error Reading Flash Used | 01/01/70 00:00 | |
| One more Hint | 01/01/70 00:00 | |
| Re | 01/01/70 00:00 | |
| Guessing | 01/01/70 00:00 | |
| Isn't this blindingly obvious? | 01/01/70 00:00 | |
| No, it is not. | 01/01/70 00:00 | |
| OK - wrong size | 01/01/70 00:00 | |
| Ok, I will find out | 01/01/70 00:00 | |
| config data | 01/01/70 00:00 | |
| LPC900 Configuration Bytes | 01/01/70 00:00 | |
| LPC900 Config Bytes | 01/01/70 00:00 | |
Why memory "mapped"? | 01/01/70 00:00 |