1am...time for the demoralized to go to bed....
Maybe someone can shed light on this in that meantime since you shared all of your various bits of code. The Teensy code is so "dumb" (having only a few dozen lines) it can't possibly be wrong!

good luck

friendofmegaman wrote:

I can only detect 70 clocks between two HSYNCs...

Do you mean between two Vsyncs? Looking back at your "logic-analysis" vsync seems to offer more of a set pattern than the clock or hsync. How many clocks should you be detecting?

friendofmegaman wrote:
Jazzmarazz wrote:

There is nothing inside of loop. I don't think...your code does anything at all right now. :S

The 4's could be some high-impedance / capacitance on the serial wire or some nonsense like that. Then again, I could be well off-base.


Loop is empty because the workflow is based on interrupt handlers. And they work fine otherwise I wouldn't get any data. In fact I tried to put some constant value there and I can see it appear in my hex dump. So this is not the problem. The code works just fine. And it seems that the only explanation of missing clocks is one I mentioned in the previous post.

Oh! I need to learn about interrupts still. I have yet to need to use one, so I never read about them. tongue

There is nothing inside of loop. I don't think...your code does anything at all right now. :S

The 4's could be some high-impedance / capacitance on the serial wire or some nonsense like that. Then again, I could be well off-base.

Well, we (friendofmegaman) has a long way to go, but this should be an easy build-in solution for it once taht time comes:
https://code.google.com/p/arduino-tvout/

friendofmegaman wrote:
Jazzmarazz wrote:

I was thinking that your baud was a little crazy. Care to reduce it to something more common?
No, I have not benchmarked a teensy.

4000000 is fairly common. But according to rvan you can use 1 and will go on maximum speed.

Is it common? I guess I just haven't dealt with it before. I normally work in the 9600 - 30K area. tongue

I was thinking that your baud was a little crazy. Care to reduce it to something more common?
No, I have not benchmarked a teensy.

rvan wrote:

I just tested this on the Teensy, and this seems to not be the case.  This is possibly different from Arduinos.  Explicitly declaring pins makes for more readable code, too.

Well, what the hell? That is very good to know, but very disappointing at the same time...

rvan wrote:

I had a think about this, and I think the only foolproof way is to store only three pixels per byte and use the remaining two bits to store new line and/or new frame markers.  Another option would be to simply count pixels (assuming we always begin sending at the start of a frame) and hope we don't drop any bytes, but that is not as robust.

I like that, 3 pixels per byte and a 2-bit marker. Serial is sure fast enough to handle that.

~snip~

Hm...there has to be a better way of separating the frames. Chances are that the new separator could still become mixed with data. Slimmer, but still not 100% mix-proof.

OH! Describe to me what is happening on the PC-end. step-by-step. I am not familiar with that software.

Hah, yeah. I copied the wrong one. tongue

I think you pasted the wrong one. tongue

813

(274 replies, posted in Nintendo Handhelds)

alexbc2999 wrote:

Are these still avalible?

PM'ed

Strayed wrote:

Kinda a noob question but what are you guys using this for?

Heh, it is a USB device which allows for you to back-up save files, ROM images and even program other ROMs to flash cartridges.

Heres the story and some basic info:
http://reinerziegler.de/readplus.htm#GB_Flasher

Pardon me for doing so, but I organized your program a tiny bit. It 'should' do exactly as it did before (working or otherwise). Can you verify this for me?
Have you changed it since this post?:
http://chipmusic.org/forums/post/206481/#p206481

http://pastebin.com/DFt5dEA3

I WANNA!!!!!!!!!!!!!!.............but we'll see.....

Looking through your code and ... I have a few comments.
1. Not naming your pins drives me nuts and I worry that just having them numbered could mix them up with variables.
2. Pins default to input, so your for pinMode for-loop is unnecessary. 
3. And as always, COMMENT UR SHIT! haha....