Closed GoogleCodeExporter closed 8 years ago
Not really it get converted into c9x internal format, no info is lost, you can
also switch later...
But maybe a popup can be implemented, but I will place on low priority.
Original comment by romolo.m...@gmail.com
on 18 Aug 2012 at 1:46
When loading an EEPROM, we don't keep it in memory. There are already Popups
opened when there is a mismatch (especially when we write the EEPROM and a
field is not supported either by c9x or the FW).
Original comment by bson...@gmail.com
on 5 Sep 2012 at 8:32
Yep, didn't know back then.
But that issue wasn't necessarily meant for the general public, but more for
developers/helpers and the simulator.
For example I use open9x, but when someone has an issue and posts his eeprom
file for review it might be an er9x file. If I open it and simulate, it will
simulate open9x behavior, not er9x behavior, and it's not obvious.
Original comment by bernet.a...@gmail.com
on 5 Sep 2012 at 8:41
When loading the EEPROM on Linux the type of the EEPROM is dumped in the
console.
Original comment by bson...@gmail.com
on 5 Sep 2012 at 8:45
Original issue reported on code.google.com by
bernet.a...@gmail.com
on 11 Aug 2012 at 5:43