YESSSSSSS
thanks a lot for going through the effort of instructions and schematics
Wireless N64 controller?
Moderator:Moderators
- blaze3927
- Portablizer
- Posts:1114
- Joined:Mon Dec 08, 2008 6:14 am
- 360 GamerTag:notjames
- Location:Australia
- Contact:
Australian Kaillera server
[url]hhttp://i56.tinypic.com/ncb0wi.gif[/url]
[url]hhttp://i56.tinypic.com/ncb0wi.gif[/url]
Re: Wireless N64 controller?
Will you be making the source available, or just the hex files?micro wrote:Thank you, thank you
Instructions including schematics and hex files are online now (see video description).
Great work btw.
zeturi wrote:If you're getting 404'd when trying to use the links in stickies, try this tutorial to find that juicy info.
Re: Wireless N64 controller?
Sorry no, I don't plan on releasing the source because source code documentation isn't complete AND it's mixed in english/german
Tidying up the documentation would cost time & effort...
Tidying up the documentation would cost time & effort...
- frontispiece
- Posts:9
- Joined:Mon Nov 08, 2010 3:45 pm
- Location:Vancouver, Canada
Re: Wireless N64 controller?
@ micro:
No way, this is amazing! Our thread was only for N64, and you went ahead and did all of them. Very impressive.
I know you are not planning on cleaning up and releasing the source code - but now that you've solved it, would you do me a favour and please answer a question that was bugging me the WHOLE TIME I was working on the N64?
Here is the question:
How did you communicate between the receiver and the N64 itself? If I understand correctly, when the N64 turns on, it sends a bunch of 0x00 "are you there/what do you have plugged in" commands on the data line, and then 0x01 "what buttons are being pressed"? What did you do with the receiver's micro in order to fake a response and get the N64 to think that there was a genuine controller plugged in?
Thanks again, beautiful work! I hope you have time to answer, that question has been bugging me for months and was the reason I gave up on it ...
No way, this is amazing! Our thread was only for N64, and you went ahead and did all of them. Very impressive.
I know you are not planning on cleaning up and releasing the source code - but now that you've solved it, would you do me a favour and please answer a question that was bugging me the WHOLE TIME I was working on the N64?
Here is the question:
How did you communicate between the receiver and the N64 itself? If I understand correctly, when the N64 turns on, it sends a bunch of 0x00 "are you there/what do you have plugged in" commands on the data line, and then 0x01 "what buttons are being pressed"? What did you do with the receiver's micro in order to fake a response and get the N64 to think that there was a genuine controller plugged in?
Thanks again, beautiful work! I hope you have time to answer, that question has been bugging me for months and was the reason I gave up on it ...
Re: Wireless N64 controller?
No problem, here's the code for speaking to the N64 console: (but not including the wireless and button conversion stuff)
If the N64 console pulls the data line low it will trigger the interrupt service routine 0 and the MCU will record the command. After the command has been sent, the MCU checks the command and it will start to send the appropriate answer (status or buttons data).
In the beginning I thought the 0xFF command just resets the controller, but evilteddy taught me that this command should also be answered with the status bytes. So thanks again for this tip
In the end I don't think my code differs very much from evilteddy's.
Spoiler:
In the beginning I thought the 0xFF command just resets the controller, but evilteddy taught me that this command should also be answered with the status bytes. So thanks again for this tip
In the end I don't think my code differs very much from evilteddy's.