On the other way I'm still interested in a possible solution, which makes me a bit unfullfilled :-(
I can understand.
But as you probably can understand, there are unexpected problems that can delay the development progress.
The situation about this issue is currently like this:
- Inter-MCU communications depends on multi-MCU implementation which is half done in 0.5 version.
- 0.5 version development is presenting several problems difficult to solve, so the base to implement everything else is not ready.
- Because the delays in 0.5, I created an intermediate 0.4.15 version and retrofited the working parts of 0.5, this took time from developing 0.5.
But now 0.4.15 is almost ready with some important features, including Arduino Shields (that was waiting for long time) and a proper Oscilloscope-Plotter.
0.4.15 development is "finished" and now on will only receive fixes.
It will be public in April 3 as "unstable".
This means that now I can focus again full time in 0.5 development.
- MCU simulation in simulide has extra complexity because MCUs are simulated by other programs: simavr for AVR, which is written in C, with a totally different style and often difficult to understand (for me at least). And it does not implement a few things needed by simulide.
As you probably already know, working out a solution for this is not trivial. It is complex and takes a LOT of time.
The idea is a new MCU simulator totally integrated in simulide that will work for all MCUs.
All the time used in implementing things based in simavr or gpsim (a lot) is time taken from this new MCU simulator and wasted is something that will be used just for a few months.
- There are literally dozens of issues like this to solve, some of them critical. Each one needing dozens to hundreds of hours of work.
Since the last summer I have been working extra time in simulide trying to solve everything.
At the end of the year I was already exhausted. In January I worked 15+ hours a day, 7 days a week (just in simulide).. to find that I had to re-write a great part the work.
Now I am beyond exhausted, I'm burn out. The only reason I keep working in this is because people like you that trusted this project and now is somehow depending on it.
- The best way for someone to implement something like this is collaborating. I, at least know how simulide works and have a rought idea of how simavr works.Conclusion:
I'm so overwhelmed that it's difficult for me to think the best path, but writting this post helped me to get a picture:
- The future is the new MCU simulator.
- I will not implement new things in simavr or gpsim.
- If someone wants to implement it, we can collaborate.
- There is no clear timeline, I'm working tirelessly in this almost for free and I will just do my best. When something is already implemented, then you can be sure you can use it.
I hope this helps.