Driver Development Kit (DDK)

cancel
Showing results for 
Search instead for 
Did you mean: 

Where can I find tDMAChannel.h

Hellow

 

Where can I find following files:

tDMAChannel.h, tDMAChannel.cpp

tDMABuffer.h, tDMABuffer.cpp

tLinearDMABuffer.h, tLinearDMABuffer.cpp

tMITE.h, tMITE.ipp, tMITE.cpp.

 

Thanks

0 Kudos
Message 1 of 5
(6,353 Views)

Download dma.zip located here:

 

http://ftp.ni.com/evaluation/labview/ekit/other/downloader/dma.zip

 

In it you will find the following sources:

 

dma.mak
tDMABuffer.cpp
tDMABuffer.h
tDMAChannel.cpp
tDMAChannel.h
tLinearDMABuffer.cpp
tLinearDMABuffer.h
tMITE.cpp
tMITE.h
tMITE.ipp

 

The rest of the examples are listed here:

 

https://lumen.ni.com/nicif/us/evalmhddk/content.xhtml

0 Kudos
Message 2 of 5
(6,343 Views)

Hellow, thanks for answer.

 

One more question:

 

u32 getCalibrationAreaOffset (const u8 *eepromMemory)

{

    return (eepromMemory[kCalibrationAreaOffset] << 😎 | eepromMemory[kCalibrationAreaOffset+1];

}

 

In function getCalibrationAreaOffset construction (eepromMemory[kCalibrationAreaOffset] << 😎 always equal 0, as since (eepromMemory[   ] have size u8. Is there sense here?

 

Thanks

0 Kudos
Message 3 of 5
(6,337 Views)

What compiler are you using?

 

Can you post your definition of u8 here?

 

 

0 Kudos
Message 4 of 5
(6,333 Views)

Hellow.

 

I use GNU Compiler Collection (4.3.3) under QNX Momentics IDE.

 

Function u32 getCalibrationAreaOffset (const u8 *eepromMemory) looks in my code as:

 

 

uint32_t getCalibrationAreaOffset (char* eepromMemory)

{

    return (eepromMemory[kCalibrationAreaOffset] << 😎 | eepromMemory[kCalibrationAreaOffset+1];

}

 

Objects of type char (and u8, I think) have size 1 byte. But then operation <Object of type char> << 8 always must be equal to 0. Am I wrong? Why?

 

What real value (offset) will getCalibrationAreaOffset return for PXI-6255?

 

Thanks

 

0 Kudos
Message 5 of 5
(6,326 Views)