MCL64 - checking a good c64 report some errors on rams and kernal char rom

[znarF54]

hi, MCL64 seems to be a great thing but i got some errors on checking a working c64 board (250407).
Before I started with MCL64 I was checking the hole hardware with my UfD Set (https://www.forum64.de/index.php?thread%2F127712-ufd-cartridge-dual-diagnose-cartridge-mit-spannungs-und-frequenzmessung%2F=&pageNo=1 which reports no error on the rams and roms.
After that I run some tests with my MCL64 the roms got a passed status.

But a check of the DRAM fails

Ans the initial test also reports failures inside the roms, which passes the single test before

Is it possible to solve these errors?
I also think that all the different board releases out there (250407, 2050425,250466, 250469 and the older ones) maybe report other results. The most of them are in my collection so I can so some tests if you would be so glad to update the code.
happy hacking and kind regards
znarF54

[MicroCoreLabs]

Hi, First question would be if you are running the Teensy 4.1 in overclocked mode? I think it needs to run at either 700Mhz or 800Mhz to have the best timing on the bus. Also set code optimization to Fastest. It is strange that the ROM test would fail even it is previously passed. Maybe there is an uninitialized variable in my code somewhere between tests. The code is easy to modify and see why the DRAM test fails for you. I suggest trying a simple write/read test and see what data is returned. Hopefully it is just a Teensy speed issue. It is also strange that many of the tests fail.. Like the VIC and color RAM. Yeah.. It does look like either a speed issue or some other signal integrity issue for your system. Please let me know how it goes! Thx -Ted

…

________________________________ From: znarF54 ***@***.***> Sent: Monday, July 22, 2024 9:54 AM To: MicroCoreLabs/Projects ***@***.***> Cc: Subscribed ***@***.***> Subject: [MicroCoreLabs/Projects] MCL64 - checking a good c64 report some errors on rams and kernal char rom (Issue #26) hi, MCL64 seems to be a great thing but i got some errors on checking a working c64 board (250407). Before I started with MCL64 I was checking the hole hardware with my UfD Set (https://www.forum64.de/index.php?thread%2F127712-ufd-cartridge-dual-diagnose-cartridge-mit-spannungs-und-frequenzmessung%2F=&pageNo=1<url> whicjh reports no error on the rams and roms. After that I run some tests with my MCL64 the roms got a passed status. mcl64.char.rom.test.png (view on web)<https://github.com/user-attachments/assets/48fd4003-a4f9-4f91-9a5c-fc145da50039> mcl64.basic.rom.test.png (view on web)<https://github.com/user-attachments/assets/607398fb-2c42-430a-b24b-e967f93814a5> mcl64.kernal.rom.test.png (view on web)<https://github.com/user-attachments/assets/da1d9af3-b5e1-4d68-8e5f-5af7778274de> But a check of the DRAM fails mcl64.dram.test.png (view on web)<https://github.com/user-attachments/assets/299513e8-29b4-4af7-9a76-cf84c2a57b0d> Ans the initial test also reports failures inside the roms, which passes the single test before mcl64.initial.test.png (view on web)<https://github.com/user-attachments/assets/9c5de2a2-53d4-473f-bd27-020eba83a1a8> Is it possible to solve these errors? I also think that all the different board releases out there (250407, 2050425,250466, 250469 and the older ones) maybe report other results. The most of them are in my collection so I can so some tests if you would be so glad to update the code. happy hacking and kind regards znarF54 — Reply to this email directly, view it on GitHub<#26>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM4AVEID67INEJ7MDADD4XLZNU2MHAVCNFSM6AAAAABLIWQWRSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDGMZSG44DSMA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>