kimjorgensen / easyflash Goto Github PK

I have found a bug in connection with the emulation of Nordic Power. To reproduce it you only have to load the CRT and then load the game "PITSTOP II" from floppy (occurs in both cases) with the Nordic Power fastloader (F5 in the Nordic Power start screen) and of course start it.

Observation: The start screen of Pitstop II is defective.

Expected behaviour: The whole game should be loaded without errors and also executed without errors. With an original Nordic Power module the problem does not occur and the game will run without errors.

Since a similar error also occurs in other Nordic Power emulations, I have gained some experience, which could be the cause: compared to the Action Replay new mode of the Nordic Power from $8000 ROM and from $A000 RAM is mapped. The write accesses to both mentioned areas are critical. Write accesses $8000-$9FFF must affect C64 RAM and must not affect the RAM of the Nordic Power. Write accesses $A000-$BFFF on the other hand must not affect the C64 RAM and must change the RAM of the Nordic Power. If you implement both areas as described and everything else as in Action Replay, it should work - I have already successfully corrected an emulation.

Please take the example files from that VICE bug report: https://sourceforge.net/p/vice-emu/patches/230/

You also find there some test code.

I'm trying to get it working in a test bench. However the reset line doesn't fire. I set the n_reset_io to '0' then wait a few Phi2 phase, then set it to 'H' however the internal resets never goes hi and hence the cart doesn't really kick off. And I keep going in circles looking at why it doesn't go hi.

Were you able to get it working in a ISE testbench?

Hi,

The mode Expert Auto-INT to write all crt at once is broken in easyprog 1.8.1 (CPLD 1.2.1) while it's working in official last version with official CPLD.

It's doing the job endless and never stop. After to have written auto-7, it start over again from auto-0....

Is this a known bug ?

Thank you

EDIT

Just discovered that my auto-7 was corrupted and that's surely the reason it's start over again.

I've been having trouble doing much with the USB interface, I'm not sure if this is the best place, but it is the only place I know of that is still active for this hardware.
It is the most recent "official" version of firmware 1.1.1 I believe it is.

I can get a small program through by spamming the command line commands done by having it entered and run pressing control+c to kill it if it doesn't go, then pressing up and enter to quickly re-enter the command and run it and repeating that untill it goes.

anything larger or more complex just won't work, I can't write a disk image, nor can I flash CRTs.

I have all the jumpers in the data positions and untill I get my SD2IEC running again or the new one arrives, I'm stuck with the USB interface

It would be great to select the Slot via EasyFlash 3 USB Utilities at EasyProg.
Example at PC:

easyflash -b turrican.crt -s 5

So, the crt will be copied to Slot 5.

Using the latest version of cc65 you'll get linker error. Last known working git-hash for cc65 is b9c688d9. This will build the .prg but it will crash during start both in VICE and on real hardware.

Which git-hash of cc65 are you using Kim?

Could you please tell me which version of cc65, acme and exomizer you use, to build the init?
And what version of gcc to build the tools!

best regards
Tulan

Hello,

Could you please add support to EasyProg to upload CRT files from uno2iec?
When I try to open a cartridge image to burn to an easyflash, I get the error message "Cannot open this file". The fast-loader is off but files are not opening for writing them to flash ROM.
There is an assembler code which I don't know. May be you could add the support of uno2iec to easyprog.

Regards,
Pavel.

The device firmware and software has been updated, but what about the software, also I can't seem to get ANYTHING working over usb (SD2IEC on it's way for that)

Hi Kim,

This is not an issue, but an info request. Together with Michael Jørgensen aka @MJoergen (also from Denmark, nice coincidence :-)) I am building the C64 core for the MEGA65 computer.

The MEGA65 sports a hardware Expansion Port that is compatible to the C64's, see this photo:

Our core is based on the MiSTer C64 core and is already extremely (as in 99.98%) compatible to the real C64. All game cartridges that I know, including more modern ones like Sam's Journey, and also the EasyFlash 1CR from Daniel Mantione work like a charme with our C64 core on the MEGA65. We can flash the EasyFlash 1CR and play games such as A Pig Quest and Eye of the Beholder.

But I am still struggling with the EasyFlash 3. Is there any chance that you share some info with me how EasyProg works? I am able to debug the signal flow between the C64 (MEGA65) and the EasyFlash cartridge via Vivado's ILA, which is a scope that is built into the FPGA. If I knew a bit more, what is happening on the software side, then I might be able to fine-tune anything that we might currently not doing perfectly right (phi2? IRQ? NMI? DMA?). But as said: EasyFlash 1CR works :-)

Here is what currently happens: I wanted to flash the EasyFlash 3 initialization package using EasyProg. EasyFlash detects the EF3's flash driver and starts flashing. After a second or two, it shows this error message:

And here is the screen that comes after the error message, so that you can see the Flash Driver, etc. :

And as an FYI: Before I ran into the situation that I needed to re-flash EF3's initialization package, I was actually able to "kind of use it" at the MEGA65 using our C64 core:

1. It did start, I was able to see the main menu
2. I was not able to start any of the cartridges visible in the main menu: The frame became colorful and then the system crashed
3. I was able to start EasyProg directly using the EF3 and it recognized the Flash Driver
4. I tried to flash a small CRT into Slot 1 (not into the system slot)
5. This did not work
6. Since then the EF3 does not start any more
7. This is why I am now working to get the flashing working first, so that I can proceed at all :-)

Is there any chance that you share some info here in this GitHub chat? Or via a Skype Chat? Or maybe via Discord? Here is an invite to the MEGA65's Discord server: https://discord.gg/UW9A5HAz We discuss the development in a closed group there, you could also DM me on Discord, my handle there is sy2002#5425

It really annoys me that when I click stop It closes the whole application instead of just ending the job it's working on.

It would also be nice (likely would require firmware/menu update also to accomodate) to have an ability to view the directory of an SD2IEC or floppy disk and be able to manage it from the application.(delete, add file, shift files around if that is possible?, and rename files)