• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 395 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

C5505 ezdsp standalone gpio?

Gregory Scharr
Prodigy 115 points

I'm using the C5505 ezdsp usb stick and have learned how to load boot images of code to the stick's EEPROM so that the code can be run in stand-alone. However, none of my attempts to use the available GPIOs (21-25) have succeeded. I'm using the methods of usbstk5505_gpio.h. Since I have had success with the GPIOs in debug mode, I'm guessing that debug mode automatically initializes something there that isn't initialized in stand-alone mode, but I don't know how to figure out what that is. How can I get the GPIO pins to work in stand-alone mode?

  • 0
    TI__Mastermind 23785 points

    Have you checked out the "Common Mistakes" in the C5515 Boot-Image Programmer wiki page on the left side of E2E page?

    http://processors.wiki.ti.com/index.php/C5515_Boot-Image_Programmer

    Regards.

     

  • 0 in reply to Steve Tsang
    Prodigy 115 points

    More questions arise from reading that:

    1) How do I know which GEL file is being used? I found more than one file that contains 5505 in its name on my hard drive.

    2) I opened one up and have little idea of what it is doing. How do I figure out what it happening and what is missing from my code?
    The code that I'm using has the following initialization:

    /* Initialize BSL */
    USBSTK5505_init( );

    /* Initialize the Phase Locked Loop in EEPROM */
    pll_frequency_setup(100);

    /* Initialise hardware interface and I2C for code */
    aic3204_hardware_init();

    /* Initialise the AIC3204 codec */
    aic3204_init();

    //GPIO_init();
    USBSTK5505_GPIO_init();

    Again, the last one doesn't appear to do anything as far as hardware is concerned. 

    3)Is the SARAM31 problem still relevant to the C5505? I've had other programs run without issue except for any GPIO methods, so if this is the problem, why would it only effect the GPIO?