Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
projects:ape65 [2015/03/21 10:59] – darron | projects:ape65 [2024/07/10 12:32] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 6: | Line 6: | ||
{{: | {{: | ||
\\ \\ | \\ \\ | ||
- | {{: | + | {{: |
+ | \\ \\ | ||
+ | {{: | ||
+ | \\ \\ | ||
+ | {{: | ||
</ | </ | ||
Line 32: | Line 36: | ||
The POSIX simulator has 48KB of usable RAM. The rest of the 64KB addressable is for ROM and console I/O. | The POSIX simulator has 48KB of usable RAM. The rest of the 64KB addressable is for ROM and console I/O. | ||
- | == PIC32MX150F128B at 40 Mhz == | + | == PIC32MX150F128B |
- | For the MX150 this simple schematic can be used to realise the simulator. | + | For the MX150/ |
{{: | {{: | ||
- | [[: | + | [[: |
+ | For the MX150 | ||
< | < | ||
p32 program mx150.hex | p32 program mx150.hex | ||
+ | </ | ||
+ | or, the MX250 | ||
+ | < | ||
+ | p32 program mx250.hex | ||
</ | </ | ||
- | The MX150 has 16KB of usable RAM set aside for the simulator. There is also 10KB ROM, a console and an I/O port. | + | The MX150/ |
- | == PIC32MX170F256B at 48 Mhz == | + | == PIC32MX170F256B |
- | The MX170 is an enhanced version of the MX150. The MX150 schematic above can be used for this chip. | + | The MX170/ |
- | [[: | + | [[: |
+ | For the MX170 | ||
< | < | ||
p32 program mx170.hex | p32 program mx170.hex | ||
+ | </ | ||
+ | or, the MX270 | ||
+ | < | ||
+ | p32 program mx270.hex | ||
</ | </ | ||
- | The MX170 has more RAM than the MX150 and 48KB is free for the simulator along with the ROM, console and an I/O port. | + | The MX170/ |
== chipKIT Pi MX250 at 40 Mhz == | == chipKIT Pi MX250 at 40 Mhz == | ||
Line 65: | Line 79: | ||
< | < | ||
- | pload program / | + | pctrl restore && |
</ | </ | ||
Line 75: | Line 89: | ||
< | < | ||
- | pload program / | + | pctrl restore && |
</ | </ | ||
Line 102: | Line 116: | ||
</ | </ | ||
- | On the PIC32 version, rather than run, we attach to the serial port of the micro. | + | On the PIC32 version, rather than run, we attach to the serial port of the micro. |
< | < | ||
screen / | screen / | ||
X | X | ||
</ | </ | ||
+ | |||
+ | or picocom. | ||
+ | < | ||
+ | picocom -b 115200 / | ||
+ | X | ||
+ | </ | ||
+ | |||
+ | To exit from screen, perform CTRL + A k, to exit picocom it's CTRL + a q. | ||
With both versions we will see something similar to what is below. | With both versions we will see something similar to what is below. | ||
Line 138: | Line 160: | ||
All the commands documented in the plus/4 user manual on page 182 onward are implemented on the POSIX version of Ape65. There is some variation, however, with the file operations. Ape65 omits the device parameter found in the original TEDMON since it serves no purpose here. | All the commands documented in the plus/4 user manual on page 182 onward are implemented on the POSIX version of Ape65. There is some variation, however, with the file operations. Ape65 omits the device parameter found in the original TEDMON since it serves no purpose here. | ||
- | See this [[http:// | + | See this {{downloads: |
EhBASIC is also included. EhBASIC is a BASIC interpreter written in 6502 assembly code. It can be started with the B command and stopped with CONTROL-S. | EhBASIC is also included. EhBASIC is a BASIC interpreter written in 6502 assembly code. It can be started with the B command and stopped with CONTROL-S. | ||
Line 168: | Line 190: | ||
</ | </ | ||
- | As per the original TEDMON, the display is updated with the opcode and operand data as each line is completed. This is is what is shown in the terminal as the above is entered. | + | As per the original TEDMON, the display is updated with the opcode and operand data as each line is completed. This is what is shown in the terminal as the above is entered. |
< | < | ||
Line 202: | Line 224: | ||
|0xF004 | |0xF004 | ||
- | == PIC32MX150F128B | + | == MX150, MX170, MX250 & MX270 == |
- | For the MX150 & MX170, | + | For these MX devices |
Writing a 0 results in the pin going LOW, writing a one leaves the pin to be pulled high or low externally. When writing a one, the port can be read as an input. | Writing a 0 results in the pin going LOW, writing a one leaves the pin to be pulled high or low externally. When writing a one, the port can be read as an input. | ||
Line 238: | Line 260: | ||
G 1000 | G 1000 | ||
</ | </ | ||
+ | |||
+ | CTRL-C will break the emulation. | ||
== Majenko SDXL == | == Majenko SDXL == | ||
Line 245: | Line 269: | ||
=== BASIC === | === BASIC === | ||
- | From TEDMON entering B will start EhBASIC. There are two start up methods. Enter C for cold initially and enter W for warm after BASIC has been stopped with CTRL-S | + | From TEDMON entering B will start EhBASIC. There are two start up methods. Enter C for cold initially and enter W for warm after BASIC has been stopped with CTRL-S. |
For the memory size option, just press enter and EhBASIC will work out the RAM size available. | For the memory size option, just press enter and EhBASIC will work out the RAM size available. | ||
Line 321: | Line 345: | ||
=== Resources === | === Resources === | ||
- | [[http:// | + | [[http:// |
- | [[https:// | + | |
- | [[http:// | + | [[https:// |
+ | |||
+ | {{downloads: |