![]() Feeding signals and stimulus from other hardware proxies, or recording in data files and played back in equivalent time. And people doing SoC these days often build into an array of FPGA when large chunks or whole designs are clocked at slower speeds. ![]() Mostly at a gate level and within functional units, ie perhaps one TIM instance, not dozens. The chip level guys are running tests and simulation to prove the functionality is as expected, not writing real-world apps as a means of getting test coverage. Keil for example had workable emulators of generic ARM7, ARM9, Cortex-M cores, but for most it's all the other clutter they are interested in. What gets super difficult is some kind of clock and gate level accuracy of particular ICs (like an entire STM32), and most people don't have time or budget for that. >By the way at the ARM developer summit today they bragged about their virtual hardware emulation tools.Īnd that's perhaps not hard if you have very generic interfaces, for example providing mass storage, network transport, user IO, or screen buffering.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |