winteriscoming
Champion
I'm not up to speed on the absolute latest in versions of the Pi, but I tend to always buy Pi 3's since the price difference isn't that big. Any reason not to just default to the highest performer?
uhmm... what doesn't work? the jvs protocol handler?Project Update:
Unfortunately a negative update this time, I tried running it on a Raspberry Pi 1st gen today for the first time (had been developing on my mac, but target platform was obviously a Pi) and annoyingly it just doesn't work.
I'm thinking that the PI can't process + reply fast enough and so its a speed issue. I will try on a better Pi2 or Pi3 later to see if that helps, or failing that attempt to make the code and linux distro more efficient.
So if anyone tries this on a Pi1 and it doesn't work, thats to be expected for now!
when you said getting wrong length, could you give more details? in raw hexs. and what the game title and in which platform?Little update:
I’ve tracked down the error on the Raspberry Pi - but it’s a wierd one.
The JVS protocol works like this:
1. The Naomi sends a sync byte
2. The Naomi sends the address of the device it wants to talk to as a byte
3. The Naomi sends the length of the data it’s about to send as a byte
4. The Naomi sends length amount of data bytes.
This all works on a Mac, and all works on a raspberry pi except for step 3 when in a game. In the test menus it works fine, but in the game it gets the length of 9 and not the correct length of 12. The data bytes after the length is sent are also correct.
So very stumped as to why it manages to get the length wrong, but everything else correct! Tonight I’m going to try adding a resistor inbeteeen the data lines to see if that helps.
Was wondering if anyone had any ideas on what might be going on?