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.

TMS320C6748: Generate a CLOCK signal

Part Number: TMS320C6748

Hi,

I have to make a communication protocol in which i'd use a clock line to make it synchronous.

The point is that i'm using an interrupt that jumps to an ISR with a high frecuency so i need to generate a clock signal that can be precise even if the interrupt occur (so i need something like hardware, not an if..else statement) and i also need the signal to be read from a pin of the target (needs to be read from an external device) and also be accesible to the target itselves (it needs to know when a rising edge happens to update the data to be sent).

Sorry for the bad explanation.

Thanks,

Juan

  • Hi Juan,

    Could you elaborate a little:
    - what are your requirements for frequency of the clock?
    - do you need the TMS320C6748 to generate the clock or it will receive the clock from an external clock?
    - what interface are you planning to use for your communication?

    Best Regards,
    Yordan
  • Hi Yordan,

    - I'm not sure about the frecuency requirements yet, but no more than 10 MHz.
    - Yes, I'm going to communicate two TMS320C6748 so one of them has to generate the clock (and be able to see that signal) and the other has to receive de signal. (Do you think it would be a better idea to use an external clock or something like that? if yes... could you give me an example?)
    - I'm not sure about what you are asking, but i'm planning to short 10 GPIOs of one board to 10 GPIOs of the other so i could have 8 lines of data, 1 for the clock and 1 for strobe or osmething like that, i'm still figuring it out.

    Thanks,
    Juan
  • Ok Juan,

    One option is to use some interface clock, but you should maybe need to add a piece of sw that keeps the interface (respectively the clock) running. This maybe least recommended.

    Another option is to get the pwm outputs to continuously generate signal with 50% duty cycle. Again this requires sw configuration that keeps the pwm outputting signal for as long as your data transaction is active.

    And the third option is to design your board so that it uses an external clock generator:
    www.ti.com/.../overview.html

    Best Regards,
    Yordan
  • Hi,

    i'll study the external clock idea.

    About the other options...

    What do you mean about interface clock?  doing it by code?

    like:

    if (count % 2)
        output = True;
    else
        output = False;

    About the pwm you mean using the eHPWM module? does that module keeps generating the PWM signal even when the main thread is doing other things?

    Thanks,

    Juan

  • Hi Juan,

    What do you mean about interface clock? doing it by code?

    I mean any SoC interface having a clk line (i.e. spi, emifa, etc..).

    About the pwm you mean using the eHPWM module? does that module keeps generating the PWM signal even when the main thread is doing other things?

    This is the problem here (same issue arises when using device interface).. you have to keep the module generating a signal within the main thread.. This may be complicated task, so I suggested to take into account using an external hw clock generator.

    Best Regards,
    Yordan
  • ok, that's what i was thinking.
    I'm going to think about the external hw clock generators.

    Thanks Yordan,
    Juan