I've sent you a PM.cyberbarter wrote: ↑Sun Sep 26, 2021 2:05 am Do you take donations. I very much would like to reward you for your efforts.
I made a couple of comments in this section about the Pi4:
Code: Select all
bcm2835gpio_peripheral_base 0xFE000000
bcm2835gpio_speed_coeffs 236181 60
I did make those changes and I updated my post to include that bit of missing information. Thanks for the catch. Would it be helpful if I ran this issue by the OpenOCD forums?hoglet wrote: ↑Mon Sep 27, 2021 6:45 pmI made a couple of comments in this section about the Pi4:
https://github.com/hoglet67/Beeb1MHzBus ... -pi-models
Did you modify these lines in raspberrypi-native.cfg?I haven't tried using a Pi4 myself.Code: Select all
bcm2835gpio_peripheral_base 0xFE000000 bcm2835gpio_speed_coeffs 236181 60
Dave
Yes, I expect they would be better qualified over there to advise you.cyberbarter wrote: ↑Mon Sep 27, 2021 6:57 pm I did make those changes and I updated my post to include that bit of missing information. Thanks for the catch. Would it be helpful if I ran this issue by the OpenOCD forums?
Hi Dave. I am in the same boat. This is my first exposer to OpenOCD. I will post an update if and when the OpenOCD forums help with a fix. As always, thanks for your assistance.hoglet wrote: ↑Mon Sep 27, 2021 7:00 pmYes, I expect they would be better qualified over there to advise you.cyberbarter wrote: ↑Mon Sep 27, 2021 6:57 pm I did make those changes and I updated my post to include that bit of missing information. Thanks for the catch. Would it be helpful if I ran this issue by the OpenOCD forums?
I'm very much a novice user of OpenOCD!
I did get a Pi1B AND Pi4B to program the EEPIZZA using OoenOCD with the ice6502.bin and ice6502.bit files.cyberbarter wrote: ↑Mon Sep 27, 2021 7:17 pmHi Dave. I am in the same boat. This is my first exposer to OpenOCD. I will post a update if and when the OpenOCD forums help with a fix. As always, thanks for your assistance.hoglet wrote: ↑Mon Sep 27, 2021 7:00 pmYes, I expect they would be better qualified over there to advise you.cyberbarter wrote: ↑Mon Sep 27, 2021 6:57 pm I did make those changes and I updated my post to include that bit of missing information. Thanks for the catch. Would it be helpful if I ran this issue by the OpenOCD forums?
I'm very much a novice user of OpenOCD!
Code: Select all
# Transition delay calculation: SPEED_COEFF/khz - SPEED_OFFSET
# These depend on system clock, calibrated for stock 700MHz
# bcm2835gpio_speed SPEED_COEFF SPEED_OFFSET
bcm2835gpio_speed_coeffs 146203 36
Do you mean the SN74LV1T125DBVR parts?
If you really need those features NOW you could risk ebay; there are some showing there (in China).If you struggle to solder fine-pitch parts, the three 74LVT125 devices (U7-9) can be omitted. You will loose two features:
- the external trigger capability (which allows a breakpoint to be qualified by a function of two external signals)
- the TSC capability (a RnW cannot now be tristated).
Yes, that will effectively disconnet the IRQ input from the 6502.
There isn't currently a similar way to disconnect reset, though it may be possible to add this if you are really stuck.
I'm not understanding what you mean by output here?
If it's possible to do this externally, that might be most expedient for you.
OK.
It would be helpful if you could share a few more details of the problem here, rather than just stating the solution you think you need.
Yes that would be most helpful.Are you trying to have IRQ disconnect automatically when single-stepping, and have it reconnect automatically when free running (after the continue command)
yes.Are you equippped to rebuild the Xilinx firmware from the github sources?
also yesDo you have a machine running Linux to hand?
I've replaced the rather unfriently special command with a set of "x" commands:
Code: Select all
>> help
ICE-65C02 In-Circuit Emulator version 0.997
Compiled at 15:12:54 on Nov 18 2021
8 watches/breakpoints implemented
Commands:
blist
...
xirq e|c|d|f
xnmi e|c|d|f
xres e|c|d|f
xso e|c|d|f
Code: Select all
>> x
xirq = Enabled
xnmi = Enabled
xres = Enabled
xso = Enabled
>> xirq c
>> x
xirq = Conditional
xnmi = Enabled
xres = Enabled
xso = Enabled
>>
See these two pages:
Actually, BRK is normally regarded as a two-byte immediate opcode, so it's reasonable to update the disassembler to treat is as such.robert_o wrote: ↑Thu Nov 25, 2021 7:30 pm The "n" instruction is great to jump over a "jsr" and it works fine for most cases. My computer (or more the OS) uses the brk opcode extensively, it is called "supervisor call" and it is used for nearly everything from printing a character, checking input, converting time and date,...
It is used with a brk followed by a one byte code (there are nearly 100 different codes). If the computer encounters a brk it generates an interrupt (internally) so the masking doesn't work - which is a good thing. I have to singlestep through the handler though or manually set a breakpoint after two bytes. It would be great if the "m" command could be extended for example "m 2" creates a breakpoint after two bytes while the "m" still behaves the way it is intended.
I was able to get the EZPIZZA programmed using a 64bit Pi4B running a 64bit beta version of the Pi OS and a current version of OpenOCD. Attached is a word.doc with my notes. Please share.hoglet wrote: ↑Sun Oct 03, 2021 8:00 am Thanks for the update Cyberbarter.
It does look like bcm2835gpio_speed_coeffs values depend on the ARM clock:There are some more examples here, some determined experimentally:Code: Select all
# Transition delay calculation: SPEED_COEFF/khz - SPEED_OFFSET # These depend on system clock, calibrated for stock 700MHz # bcm2835gpio_speed SPEED_COEFF SPEED_OFFSET bcm2835gpio_speed_coeffs 146203 36
https://github.com/bunnie/netv2mvp-scri ... de.cfg#L23
Dave