| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
debugging codenet
My retro-replay+rr-net has stopped working. I'm using codenet-0.4, all the packet replies are fine (complete with correct sequence number), but after a -x command, all the bytes that have arrived at the c64 have their high bit set.
Any ideas? (Host is running El Capitan if that makes any difference.. Cart has TFR v0.6, board revision October 2004) |
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
i'd try with another PC/OS first, so you on what end the problem is (i'd rule out the c64 end in this case, but thats just a guess =P) |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
Excellent plan. Now I just need to get hold of another computer (my SO's laptop's running the same OS, and nothing else in the house has ethernet.) Wonder if I can borrow a Pi from my sister-in-law
|
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
..meanwhile am contemplating writing a short routine that only uses opcodes/operands greater than $7f to that writes a slightly saner routine that decompresses a stream that's been padded with a "1" at the start of every seven bits :-/ |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
definitly sounds easyer than to connect a disk drive, and use native tasm :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
LOL |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quote: ..meanwhile am contemplating writing a short routine that only uses opcodes/operands greater than $7f to that writes a slightly saner routine that decompresses a stream that's been padded with a "1" at the start of every seven bits :-/
Nice challenge! :) Actually only using ops $80-$ff doesn't look so bad. Loads and stores, inx/dex, compare, subtract and relevant branches are all there. No shift instructions though. |
| |
Krill
Registered: Apr 2002
Posts: 2980 |
Quoting ChristopherJamall the bytes that have arrived at the c64 have their high bit set In your place, this'd make me check the RRnet hardware/connection first. Reminds me of connection/contact/signal issues that cleaning or swapping a (non-IC) part would fix. But, of course, could also be a broken IC, or a problem anywhere else.
Anyhow, have had any progress yet? Good luck! |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
Quoting KrillQuoting ChristopherJamall the bytes that have arrived at the c64 have their high bit set In your place, this'd make me check the RRnet hardware/connection first. Reminds me of connection/contact/signal issues that cleaning or swapping a (non-IC) part would fix. But, of course, could also be a broken IC, or a problem anywhere else.
All good points. I've tried reseating/cleaning both the cart and the ethernet adapter to no avail. Codenet on the 64 end seems happy that it can see the registers at least. ("rr-net found. cs8900a revision d")
Quote:Anyhow, have had any progress yet? Good luck!
Sadly things are backsliding; all I'm getting at the host now are timeouts. Could be anything from my network settings to my thunderbolt port to my thunderbolt->ethernet adaptor to my cable to the rr-net or rr. Going to borrow my wife's laptop tonight or tomorrow to try and rule out the first two at least. And thank you! |
