Lynx Games Not Dumping

[the16bitgamer]

OSCR firmware version

2025 fw15.3

OSCR hardware version

HW3 Alter

Attach OSCR_LOG.txt file here

OSCR_LOG.txt

System used

Select a system

Describe the issue.

Got in my V3-Alter recently and while everything works with it, including other Atari Adapters. My Lynx adapter doesn't. I only have 4 games and they all have the same(ish) error as above.

I've tested all 4 games with my Lynx and they are working.

I am hoping it's something simple, or I messed up some how.

AUDIN=0 BLOCK=2048

[the16bitgamer]

Here is the video of the issue, I just flashed the latest firmware

https://youtu.be/QQ8WeNIPNvw

[the16bitgamer]

I flashed an older version of the software v14.7 and it was working I'm not skilled with this kind of coding but I'll see if there is any changes and see if I can fix it.

[PsyK0p4T]

I've just tried the current code (v15.3) with an hardware v3 and v5, and both seem to work fine here :

Can you try various things ?

• make sure the 5v switch is ON, and all others are OFF.
• disable many modules, or just keep the Lynx one, then retry to dump your carts.
• make sure all cart pins are super clean. You can use a simple white rubber to polish them.
• maybe try the v15.2 release and let us know how it reacts ?

[the16bitgamer]

Per your instructions, I made sure the 5v switch is ON, and the other 3 switches were off. I also made sure that the game loads on a Lynx and is playable before inserting it into my OSCR to ensure that it's contacts are clean, and that I was able to dump it on 14.7 before testing on 15.2.

So after I verify that the cart was dumping accurately on 14.7, I ran 3 tests.

Test 1) A fresh download of 15.2 from release. And leaving the defaults on and turned on Lynx. This failed.

Test 2) I turned off everything in Module Config except Lynx. This also failed.

Test 3) I turned off everything in Module Config except Lynx and Options Config. This also failed.

If you can tell me how to get the current build from 15.3 I would love to test it.

[the16bitgamer]

Copied the files from the Cart Reader on the master branch. About claims it's 15.3 and when I tried to dump it had the same issues.

14.7 is the only build which is able to dump carts on my unit.

If you need any logs or would like me to test anything please let me know

[sanni]

Might be related to these compiler warnings:

C:\Users\sanni\Desktop\V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\LYNX.ino: In function 'void compareStride_LYNX(uint8_t, int, int)':
C:\Users\sanni\Desktop\V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\LYNX.ino:137:21: note: in expansion of macro 'max'
  137 |     lynxBlockSize = max(lynxBlockSize, stride << 1);
      |                     ^~~
C:\Users\sanni\Desktop\V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\LYNX.ino: In function 'bool detectCart_LYNX()':
C:\Users\sanni\Desktop\V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\LYNX.ino:152:21: warning: comparison of integer expressions of different signedness: 'int' and 'const size_t' {aka 'const unsigned int'} [-Wsign-compare]
  152 |   for (int i = 0; i < DETECT_BYTES && lynxBlockSize < LYNX_BLOCKADDR; i++) {
      |                   ~~^~~~~~~~~~~~~~
C:\Users\sanni\Desktop\V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\LYNX.ino:180:1: warning: no return statement in function returning non-void [-Wreturn-type]
  180 | }

I have changed the code so they don't happen anymore, maybe this fixes it.

Replace LYNX.ino in V15.2_Portable\Arduino IDE\portable\sketchbook\Cart_Reader\ with the one extracted out of this zip: LYNX.zip

Although I feel like I should have changed "const size_t DETECT_BYTES" to "int DETECT_BYTES" instead of changing "int i" to "size_t i" because "size_t" sounds very suspicious.

So here is an alternative fix, maybe try both:

LYNX.zip

[the16bitgamer]

Both Fixes works with my games without any issues. Tested with Cyberball and Scrapyard Dog.

@sanni you are good to go!

There is an odd bug I am looking at for games under 1024 but I'll make a new issue for that.