• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 359 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.

HyperLink Rx Side address Translation

Nithin Ramesan
Intellectual 270 points

Hi.

I'm reposting this question as I didn't get a satisfactory answer the first time 'round.

In the HyperLink MCSDK example program, according to the HyperLink User Guide and Training Documents,  rxSegVal is overlaid on the 16 MSB of the incoming address on the receive side during address translation, in order to obtain the address at which the incoming data is written. However, in the example program, rxSegVal is calculated from the value of the address of dataBufferSrc, which is a variable that is declared on the receive side but has nothing to do with receiving data.

Why is rxSegVal dependent on the value of &dataBufferSrc? Is it possible to define it as some other value?

  • 0
    TI__Mastermind 28085 points
    Hi,

    In hyperlink example, DSP1’s memory are mapped to DSP0’s memory window from 0x40000000 to 0x50000000, the DSP0 can access all memory types in DSP1 including LL2 (Local L2), MSMC (Shared L2) and DDR just like access DSP0’s local memory. In DSP0, all masters access same outbound window at 0x40000000, but they may actually access different memory space in DSP1, because the PrivID of the masters in DSP0 is carried with address and the inbound memory segment configuration of DSP1 is set up separately for different PrivID.

    Set up dataBufferSrc to be a hyperlink address that will point to dataBuffer address on the remote side.

    Thanks,