troll baiting?

786

(119 replies, posted in General Discussion)

and next:

Yes, because I am a snob.

787

(8 replies, posted in Nintendo Handhelds)

Geez you're even in Detroit. I'll give you a grey shell for the cost of shipping....

oops...

789

(8 replies, posted in Nintendo Handhelds)

I can't even address the main question until you answer my own: why would you paint a red-boy white?!

Does anyone know what sort of data is stored in VRAM? Is it simply active sprites, windows, etc? or might it be something useful to us?

791

(13 replies, posted in Nintendo Handhelds)

At first I was like "lol" then I started playing with it. I like it and I hope to see additions like:
inverted screen
clear St+Sel
thats all for now.

kudos

I took a few minutes to find the cycles per instruction, but all I can find are the cycles per assembly op-code. Obviously the code is not in assembly. Is there a way to disassemble the *.cpp.hex file (found in the working directory after compiling)? If we could do that, then you could get the actual cycles per instruction and find out if the interrupts are taking too long.

Is that still a possible cause of the problem?

793

(4 replies, posted in Trading Post)

usb or no?

794

(6 replies, posted in Nintendo Handhelds)

Gamer_freak8520 wrote:
PianoGameboy wrote:

How was it broken in the first place and what did you do to fix it?

the ribbon cable was snapped so i stripped it and it works but there are the columns.

You mean the white ribbon cable that connects the front PCB to the back PCB? That would not cause stripes if it was busted, but entire outages.

Scratch that. I think I will try out my new Raspberry Pi since it has built in video outputs. No idea where start with programming taht thing though...

friendofmegaman wrote:

I though about deploying a logic analyzer. What they do (if understand it correctly) is record a sample to the memory (e.g. flash) and then you read it to PC. A good thing would be to know how to build one and use for real time data processing.

Another option is FPGA. The way it works allows really fast signal processing. In fact in can be clocked by the gameboy and still be able to send data to PC. This is what a guy named Snesy did. I tried to contact him through several sources, but without any luck.

Next - Nitro's suggestion to use uC as clock master. I don't understand how (in case of Teensy at least) it solves the issue of only 24 clocks available to do something with the data? 24 is an optimistic estimate.

Finally - DSP. I think logic analyzers are built upon these. However I've no idea where even start with that.

Any other options?

Before diving into the next idea it would be great to figure which of them will (given enough effort) guarantee success. Not some ugly hacked code that will fail 50% of time, but neat and reliable solution. We know it was done on FPGA.

Pros: it will solve this problem, it should suffice to have even more outputs (VGA and composite) and it can be even used as an adapter to plug a controller - so the whole "desktopification" module can be done with one (probably quite big though) board. Since it can have multiple clock domains, and programmed to do virtually everything (no teleportation though).

Cons: Prototyping boards from Atmega (as an example) cost around $80, not only they are programmed in very strange way I can't find any good comprehensive introduction in programming FPGA.

I need to reflect on this... and wank...

Bringing this post back to our attention, I have a small FPGA board that I still need to use. The only reason I haven't yet is because I wrote a Verilog program once and no matter what CPLD or FPGA I chose in the settings, the compiled program was always too large for them. Since there was nothing I could remove from my code, I just gave up altogether on using an FPGA for that project and set it aside. It may very well be time to pull it back out.

I will need for you to fill me on exactly what the h and v sync, clock and data traces do, or at least show me a datasheet on them. I may have to skip the "serial.write" function and move straight to VGA video.

797

(1,620 replies, posted in General Discussion)

Crossfire! You sunnabitch. tongue
I like your cooler. I have the ThermalTake version.

BTW, I only drink IPA. sqwee~ ^_^

C U THER

I would say that it is enough, but we are missing something obvious. What if, 96MHz is in fact 'too' fast. Could you possibly be reading data that has yet to be populated on D0 and D1? There is always a propagation delay, but it still doesn't account for mostly 4's...My excuse is that Im tired. Don't blame me for my ramblings. tongue