Yes, the first diagram represent a "0" and the second a "1"
I was thinking to split a "n64" bit in 4 bits
so 0b0 will become 0b0001
so 0b1 will become 0b0111
I need to send 0b000000011 to the controller and it will answer me 33 bits (4 bytes of data and 1 bit stop)
The N64 controller data consists of a 32 bit (4 bytes), which gives you the status (on/off) of all buttons and the joystick position (2 bytes) and one stop bit. The array is built up like this:
So 0b000000011 will become 0b000100010001000100010001000101110111 so 36bits
and the answer will be a 132 bits message.
I'm not familiar with the protocol (UART, SPI), but I notice the SPI use two entries to deal with the emitter (MOSI) and the receiver (MISO).
but the n64 controller use a unique cable to transmit the data. how can I plug this king of things to the espruino ?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Yes, the first diagram represent a "0" and the second a "1"
I was thinking to split a "n64" bit in 4 bits
so 0b0 will become 0b0001
so 0b1 will become 0b0111
I need to send 0b000000011 to the controller and it will answer me 33 bits (4 bytes of data and 1 bit stop)
The N64 controller data consists of a 32 bit (4 bytes), which gives you the status (on/off) of all buttons and the joystick position (2 bytes) and one stop bit. The array is built up like this:
So 0b000000011 will become 0b000100010001000100010001000101110111 so 36bits
and the answer will be a 132 bits message.
I'm not familiar with the protocol (UART, SPI), but I notice the SPI use two entries to deal with the emitter (MOSI) and the receiver (MISO).
but the n64 controller use a unique cable to transmit the data. how can I plug this king of things to the espruino ?
Hum I see