Problems connecting PS2 controller to Axon

JadeKnight · #1 09-24-2009

I followed the tutorial on the SoR site (cut and paste the code) (http://www.societyofrobots.com/membe...rials/node/200), however I can't seem to get it to work. It basically loops forever trying to confirm the controller is in analog mode (waiting for a 0x73 byte). The PS2 controller (genuine sony brand) does get put into analog mode (red led turns on), however the data received from the controller is always 0 causing the init loop to go on forever. I've tried different delays between the clock pulses, etc, but nothing helps.

Here's the real kicker, if I turn off the Axon, I correctly get the 0x73 byte (and the 0x5a 'ready' byte) EVERY TIME, along with a few frames of valid controller data before the telnet connection, and the Axon, die out. It does not appear to be random input pin behavior when the Axon is turned off.

Something about turning off the Axon causes the code to work, in it's last dying breaths...

Any help would be appreciated.

Tyberius · #2 09-24-2009

I seem to recall reading that the Axon does not run its code upon boot, rather only after a reset. Have you tried that?

JadeKnight · #3 09-24-2009

The code is running, as it posts various status messages and each failure to 'connect' to the the PS2 controller in the telnet session (along with all the bytes received from the PS2 controller). It just doesn't get anything back from the PS2 controller until I turn off the power switch.

Could turning it off, and the slow power down due to the huge capacitor, cause the speed of the processor to go down? Like normally it's running to fast to talk to the PS2 controller at 16MHz, but as it slows down/powers down, it finds a good speed to connect? I've tried increasing the delays at various points during the TX/RX to the controller, but it didn't help, so I am not sure of this theory.

Has anyone else successfully connected a PS2 controller to an Axon, or other AVR MCU (Using C/C++)?

(Oh, and it does immediately run the program after uploading a new .hex or turning on the power. I've added a 10 second countdown at startup so I could connect a telnet session before things get going.)

Tyberius · #4 09-24-2009

Ah okay, was worth a shot. I'll get John from SoC over here and have him take a shot at this. I haven't had time to dive into the Axon platform yet, so I'm sort of shooting in the dark.

LinuxGuy · #5 09-24-2009

Quote:

Originally Posted by Tyberius

I seem to recall reading that the Axon does not run its code upon boot, rather only after a reset. Have you tried that?

The default is to require pressing the user button before code starts to execute. I commented that out in Axon.c (mine is called walter.c) and now code starts at power up.

Code:

    /*********ADD YOUR CODE BELOW THIS LINE **********/

    //wait until user pushes button
    while(!button_pressed());  // <--- comment this line out to autostart code

    //reset all timers to zero
    reset_timer0();
    reset_timer1();
    reset_timer2();
    reset_timer3();
    reset_timer4();
    reset_timer5();

    while(1)
        {
        control();//uncomment this for your code (and use control.c only to program)

        //servo_controller();

       delay_cycles(100);//an optional small delay to prevent crazy oscillations
        }
    /*********ADD YOUR CODE ABOVE THIS LINE **********/

8-Dale

Tyberius · #6 09-24-2009

Quote:

Originally Posted by LinuxGuy

The default is to require pressing the user button before code starts to execute. I commented that out in Axon.c (mine is called walter.c) and now code starts at power up.

8-Dale

Thanks for the clarification! I couldn't find that post for the life of me.