Well, what I mean is a simulator that actually ties into a programmed microcontroller. Knew about the analog simulators and tried a few but something that actually sees code and all the peripherals. Wishful thinking I'm guessing.
Well, what I mean is a simulator that actually ties into a programmed microcontroller. Knew about the analog simulators and tried a few but something that actually sees code and all the peripherals. Wishful thinking I'm guessing.
That is part of the core function of Proteus. It smooths the whole process from create schematic, run and debug code (not sure about PBP support but Proton is supported natively) to create PCB. The main problem aside from imperfect simulation, is that your choosen PIC device may not be supported.Well, what I mean is a simulator that actually ties into a programmed microcontroller. Knew about the analog simulators and tried a few but something that actually sees code and all the peripherals. Wishful thinking I'm guessing.
George
The point about a traditional debugger is that it has no connection with the real world, switches, lights, spi peripherals etc. etc. Having said that you can use Proteus as a single step ot breakpoint debugger.
Yes you can write stubs to test programmes interaction with hardware but how do you test the stub.
The point about something like Proteus is that in theory potential errors are reduced because each stage relys upon the previous one rather than a series of steps in a project each independent from each other. Weather thats worth the price can only be decided person who pays.
George
Bookmarks