SimulIDE trunk Tester builds.

New build at Rev 1530 uploaded.

Check first message in this post.

@Fizik_S:
Check your subcircuit displays:
- Led positions has been improved.
- 7 segment display appearance improved.
- Now you can place Pins at half grid cell.

Seven-segment displays look much better. Thanks for the improvements.

A user from a Russian-language forum found a problem in a program with a Russian interface: the menu items of the components "Switches", "Connectors", "Other" are not disclosed. There is no such error in the previous version.

Fizik_S wrote:A user from a Russian-language forum found a problem in a program with a Russian interface: the menu items of the components "Switches", "Connectors", "Other" are not disclosed. There is no such error in the previous version.

Thanks to that user. I will have a look.

Fizik_S wrote:A user from a Russian-language forum found a problem in a program with a Russian interface: the menu items of the components "Switches", "Connectors", "Other" are not disclosed. There is no such error in the previous version.

Solved at Rev 1539.

An error in the operation of the logic analyzer. After the simulation stops, signal graphs remain on the screen. After moving the window, the contents are cleared. The error appears only when the analyzer is connected to complex circuits containing several chips.

An error in the operation of the logic analyzer. After the simulation stops, signal graphs remain on the screen. After moving the window, the contents are cleared. The error appears only when the analyzer is connected to complex circuits containing several chips.

Thanks, I will have a look.

Processors Z80, MCS6502 do not work. In SimulIDE-R1452, the MCS6502 processor is running. Test schemes in the attachment.

Processors Z80, MCS6502 do not work. In SimulIDE-R1452, the MCS6502 processor is running. Test schemes in the attachment.

About 6505: as I understand it, RDY Pin must be high:
"A low input logic level on the Ready (RDY) will halt the microprocessor in its current state."

About Z80: I don't know, maybe vranik can have a look.

@Fizik_S:

6502 is not completely finished, I think it is near to completion, but I haven't tested all the instructions and control lines, just that it can read an execute some instructions.
So the Reset sequence, read/write to external memory and some control lines are working:




If someone wants to test it, the first step would be to ensure that the instruction set is working correctly.

Also note that I'm not an expert in 6502, I started this as a proof of concept for MPUs, so to make this work correctly some help will be needed.


The rest of the ICs of the family (6522 and friends) are in a very early state of development and are being built as scripted components.
Also as a proof of concept for scripted components.

6522 script is not far from completion, but not fully functional yet (data/MCS65/6522/6522_core.as).

I translated version 1530 to English interface. I work in it now. The program works better than with Russian.

Hi Alex.
Which problems do you find in Russian version?

The problem is described in post #77 of this topic.

arcachofo wrote:Hi Alex.
Which problems do you find in Russian version?

Switching elements did not open.
 I also have a request for you. The latest models made by the Physicist are to be put in subsequent versions.

Fizik_S wrote:The problem is described in post #77 of this topic.

Alex68 wrote:Switching elements did not open.

Ok, that issue is already solved.
I was not sure if there is some other problem.

Alex68 wrote: I also have a request for you. The latest models made by the Physicist are to be put in subsequent versions.

Yes, I will do it.

Now I'm mostly focused in fixing issues in version 1.0.0. I think it is almost done.
I'm also creating new tutorials for 1.0.0.
When this is done and 1.0.0 "stable" is published, I will focus on development version again.

I hope that the breakpoint issue (while debugging an AVR assembly code) was fixed too.

Sometimes, removing a breakpoint removes its yellow square only.

I noticed that this likely happens when the cursor is on a breakpoint (the debugger halted) and I like to remove it.
So, in order to ensure its removal, I execute first one or more instructions to let the cursor leaves the breakpoint, then I remove it.

In case a breakpoint cannot be removed (lack of its yellow square), I save and close the 'asm' file. Then I delete its 'brk' file before reloading the 'asm' file.

KerimF wrote:I hope that the breakpoint issue (while debugging an AVR assembly code) was fixed too.

Sometimes, removing a breakpoint removes its yellow square only.

I noticed that this likely happens when the cursor is on a breakpoint (the debugger halted) and I like to remove it.
So, in order to ensure its removal, I execute first one or more instructions to let the cursor leaves the breakpoint, then I remove it.

In case a breakpoint cannot be removed (lack of its yellow square), I save and close the 'asm' file. Then I delete its 'brk' file before reloading the 'asm' file.

Yes, this issue is solved.

In addition there are some other issues solved, for example:
Now it does not save .brk file if there are not breakpoints.
And the breakpoint moves with the line (if you add or remove lines before the breakpoint).

For the R1530 version:
1. The program closes at the start of the simulation if MCS6532 is present in the circuit.
2. The program closes when the "Open MCU monitor" command is executed

For the R1530 version:
1. The program closes at the start of the simulation if MCS6532 is present in the circuit.
2. The program closes when the "Open MCU monitor" command is executed

Yes, sorry, 6532 is completely unusable right now.

I also have to explain the last changes in subcircuits, most of them are improvements, but there are some constrains as well, for example: subcircuits type "Logic" don't work in "Board Mode".

Does MCS6532 work in the program SimulIDE_R1452?
I want to test the MCS6502 processor. Most circuits with this processor use MCS6532.

Does MCS6532 work in the program SimulIDE_R1452?

No it does not work at all.
It would not be too difficult to make the IO ports work, but the timer and some other thing need an script.

Thanks to the Alex68 post ( https://simulide.forumotion.com/t1405-address-bus-processor-z80-test ), I was able to detect the Z80 error. The processor does not process the reset correctly. I have put together a simple scheme that works correctly after running the simulation. After pressing the "Reset" button, the processor "freezes". I will continue testing.

Thanks to the Alex68 post ( https://simulide.forumotion.com/t1405-address-bus-processor-z80-test ), I was able to detect the Z80 error. The processor does not process the reset correctly. I have put together a simple scheme that works correctly after running the simulation. After pressing the "Reset" button, the processor "freezes". I will continue testing.

Thanks, not sure if I can find the problem but I will have a look.

Note that the Mcu Monitor shows a lot of internal information useful to debug:

About 6532:
I cleaned the files and implemented basic IO functionality.
At least now it does not crash and works to Read/Write IO Ports and RAM.
Interrupts and timers are not working.
Files attached.

Works in R1530.

And here a short video explaining how to install files and run the test program, (and edit, compile and upload the script if you want):

It is possible to debug Z80.
There are still some issues to fix, and depends on the assembler, but it is possible:

About Z80: I don't know, maybe vranik can have a look.

I am on holiday now. I will look at it next week. Please be patient.