• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 189 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.

TMS320F28388D: How to use #define in CLB simulation

Jerome Manhes
Prodigy 90 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi

I am working with multiple CLB and I do my simulation with GTKwave.

For the moment I use high(N), low(N), rpt(N) and rpt_end. Everything works but I need to generate complex stimulus and I have hundreds of line of high and low.

in spruir8b doc I see that there is a #define for macros.

How can I use it ? Is there examples ?

Sincerely.

Jérôme

  • 0
    TI__Mastermind 27750 points

    To clarify, you want to generate complicated input signals to use for your CLB  simulation?

    Are you familiar with the input designer tool that's included in CLB sysconfig?

    thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 90 points

    Hi Luke

    Thank you for your reply.

    For the moment I use the boundary inputs (Simulation Only) with the custom waveform code in the Tile Design of Sysconfig.

    I generate a UART (8N1) signal at 12.5Mbits/s and I first wish to replace some parts of my code with more friendly values. 

    For example, for the moment I use this kind of stimulus (for one byte but I have dozens of bytes):

    low(8) - start bit
    high(8)
    low(8)
    low(8)
    low(8)
    low(8)
    high(8)
    high(8)
    low(8) - 0x86
    high(8) - stop bit

    I would prefer to use something like:

    #define START_BIT (low(8))

    #define STOP_BIT (high(8))

    #define WORD_0x86 (high(8), low(8), low(8), low(8), low(8), high(8), high(8), low(8))

    ->

    START_BIT

    WORD_0x86

    STOP_BIT

    Is it possible to do so? This is to simplify the debug of my code (the words in my push fifo reg)

    Sincerely.

    Jérôme

  • 0 in reply to Jerome Manhes
    TI__Mastermind 27750 points

    Hi Jerome,

    There seems to be support for #define for custom input definitions. Unfortunately I cannot find much documentation on this. I would suggest trying different syntaxes in SysConfig until you don't see an error message. In the meantime I will debug this on my side to determine what the format requirements are.

    Thank you,

    Luke