In any case, let me get in touch with Keil and see what their thoughts are on bidirectional updates.

We can't do that. Not because we Can't but because we are not always the ones who provide the chip descriptions and other details. We work closely with many chip vendors and some of them maintain their own device descriptions. And, they all have unique namings that they want fixed.

Of course, if there are errors or omissions, we would like to know about them. We have several employees who maintain different aspects of the database. We, of course, add every device we know about no matter what level of support we provide. We even leave in obsolete and EOL'd parts.

The Keil Device Database(tm) is a very huge database of everything we can find out about each device. In addition, our database includes assembler, compiler, and linker settings for the Keil tools (not that Craig really wants to list those kinds of things), header files, data sheets, startup code, and numerous other tool settings. This database is used to generate the Device Database used in the uVision IDE. Attempting to maintain bi-directional updates would ultimately end up with corrupt or unusable devices in uVision.

Jon