easyprog 1.7.1 Expert auto-int broken

Question

easyprog 1.7.1 Expert auto-int broken

Closed this issue 5 years ago · 9 comments

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.

Answer 1 · 2019-03-05T18:23:00.000Z

Finally tried again with a valid auto-7.CRT and this fonction in Easyprog 1.8.1 is definitively broken.

You can reproduce this while using the AUTO-int fonction in expert menu to write all the crt at once on the EF3......

Answer 2 · 2019-03-12T20:58:03.000Z

Hi,
I'm not able to reproduce this behaviour. I just tried twice with two different set of CRTs and the program stops after auto-7 as expected.
/Kim

Answer 3 · 2019-03-12T21:03:50.000Z

Hi, Strange, I did not had this problem with the old version. I had this with different CRT sets and with 3 differents EF3. I will try this again with another SD card. Can it be it’s coming from something with the new firmware/software in combination with my SD2IEC ? I’ve this one : https://www.ebay.com/itm/NEW-2018-SD2IEC-SD-Card-Reader-for-Commodore-64-128-VIC20-1541-C64-C128/163086890817 Seb

…

On 12. Mar 2019, at 21:58, Kim Jørgensen ***@***.***> wrote: Hi, I'm not able to reproduce this behaviour. I just tried twice with two different set of CRTs and the program stops after auto-7 as expected. /Kim — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Al6xPcFr_8UHGJayQjVsfJH1_jTTwaGuks5vWBTbgaJpZM4bda33>.

Answer 4 · 2019-03-13T17:52:17.000Z

Did you verify all the CRTs in VICE, or did you try to flash the individually? Especially pay attention to the size of the CRTs, they should not be bigger than one megabyte.

There was no change regarding reading from SD2IEC in the new version, but it is possible that I made a mistake somewhere. You could try to downgrade the firmware and EasyProg and see if the problem persists.

Answer 5 · 2019-03-13T22:15:48.000Z

Hi, I did some more testing…. I tested the same procedure with CPLD 1.2.1 and also with CPLD 1.1.1 With known working CRT set. All results are same with both CPLD versions. It can write all slots and stop after the last slot (7) is written if I use the easyprog version 1.7.0 It’s as it should be. Note that I could not find a 1.7.1 version in Skoe download page. Now if I am using the easyprog Version 1.8.1, it writes all slot from 0-7 and does never stop. It start over again when slot 7 is finished…… There should be a bug somewhere in easyprog 1.8.1 but it’s very curious you can’t reproduce it. Maybe it’s something related to easyprog 1.8.1 and my SD2IEC….. For me it’s 200% sure there is something, I can reproduce this each time I am using easyprog 1.8.1 with different CRT sets and with both CPLD 1.1.1 and 1.2.1 firmware. Regards Seb

…

On 13. Mar 2019, at 18:52, Kim Jørgensen ***@***.***> wrote: Did you verify all the CRTs in VICE, or did you try to flash the individually? Especially pay attention to the size of the CRTs, they should not be bigger than one megabyte. There was no change regarding reading from SD2IEC in the new version, but it is possible that I made a mistake somewhere. You could try to downgrade the firmware and EasyProg and see if the problem persists. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Al6xPTUwBJBKgnaOn4OCET2c6iYTd8e_ks5vWTrSgaJpZM4bda33>.

Answer 6 · 2019-03-16T15:25:54.000Z

I believe that EasyProg 1.7.1 only exist in source code form and never was released. But I did notice the following in the CHANGES file for that version:
Auto test + init executes the torture test before flashing
Is that what is confusing you? The torture test runs through all slots and when it is done the CRTs are flashed.
The torture test can be canceled using RUN/STOP

Answer 7 · 2019-03-16T15:34:24.000Z

Oh yes, that’s probably this !!! The 1.7.0 is directly flashing all the slot, no othe test are perfomed….. When updating to the 1.8.1, I saw it flashing all the slots and starts over again. I thought it was wrong as I never saw this before. No I understand, that’s the 1.7.0 that does differently by not doing the torture test. I will try again without stoping the process or using the RUN/STOP test to jump directly to the flashing slots process. It seems you lost your time with me. But I would have not figured this out myself as I never saw the 1.7.1 version or the change log…. Thank you and sorry…. Seb

…

On 16. Mar 2019, at 16:25, Kim Jørgensen ***@***.***> wrote: I believe that EasyProg 1.7.1 only exist in source code form and never was released. But I did notice the following in the CHANGES file for that version: Auto test + init executes the torture test before flashing Is that what is confusing you? The torture test is runs through all slots and when it is done the CRTs are flashed. The torture test can be canceled using RUN/STOP — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Al6xPfjf-keBEPfE-kHEy9Zl3l9FRnQ1ks5vXQ0CgaJpZM4bda33>.

Answer 8 · 2019-04-16T06:09:36.000Z

I assume this is resolved, otherwise feel free to report a new issue.
/Kim

Answer 9 · 2019-04-16T10:07:20.000Z

Hi, Sorry, I forgot to reply you. It's 100% working. As you said, I just had to skip the stress test with run/stop. I feel a bit stupid..... Thanks. Regards Seb Le mar. 16 avr. 2019 à 08:09, Kim Jørgensen <notifications@github.com> a écrit :

…

I assume this is resolved, otherwise feel free to report a new issue. /Kim — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Al6xPZQ23vmvFBU8_uc60Zzp4cqwuHDuks5vhWkhgaJpZM4bda33> .