Sorry for the late turn around, just getting back into my lab. Now that this is working, I have a few questions.
Looking at the code you provided, how can I adapt your fix to the other transfer sizes (8 bit, 16 bit, and 32 bit)?
I am also curious on why this addition was made to the canDoDMA ...
Search found 6 matches
- Thu Apr 16, 2015 3:07 pm
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
- Tue Apr 14, 2015 6:08 am
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
Re: MOD54415 DSPI CS Assertion
Well, that's the fifoCmd variable that gets or'ed onto in front of the data chunk. Specifically the CTAR selection for configuring between the 16-bit and 8-bit chunks to be transferred. Line 486 of dspi.cpp. That said, I went a head and fixed the bug that was preventing this from working and I'm ...
- Sun Apr 12, 2015 3:21 pm
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
Re: MOD54415 DSPI CS Assertion
Now, all that said, just confirming, you are trying to get this working with DMA, and not just having the issue that the driver fails to deassert in 24 bit mode, correct?
Correct, I would like to get this working with DMA just because
of the amount of data moving.
The the interrupt control works ...
Correct, I would like to get this working with DMA just because
of the amount of data moving.
The the interrupt control works ...
- Fri Apr 10, 2015 8:30 am
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
Re: MOD54415 DSPI CS Assertion
Update:
Updating to the latest Netburner Tools, 2.7.1 Beta, does not fix the issue. Any insight into this problem?
-Matt
Updating to the latest Netburner Tools, 2.7.1 Beta, does not fix the issue. Any insight into this problem?
-Matt
- Wed Apr 08, 2015 9:06 am
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
Re: MOD54415 DSPI CS Assertion
Looking through the DMA Driver, I cannot find where the command register for the SPI peripheral is concated on to the transmit buffer. I see the driver setups the proper ctars but not the command register.
Would I need to mask the command register on my transmit buffer for each spi frame?
Would I need to mask the command register on my transmit buffer for each spi frame?
- Wed Apr 08, 2015 7:18 am
- Forum: NetBurner Software
- Topic: MOD54415 DSPI CS Assertion
- Replies: 9
- Views: 5841
MOD54415 DSPI CS Assertion
//Setup Code Below
#define ADCSPI 1
#define dspiBaudRateADC 70000000
#define transferSizeBitsADC 24
#define CSPolarityIdleADC 0x0E //Chip select polarity at idle
//DAC Idle High 0x0F
//ADC Idle Low 0x0E
#define DACSPI 2
#define dspiBaudRateDAC 25000000
#define transferSizeBitsDAC 8
#define ...
#define ADCSPI 1
#define dspiBaudRateADC 70000000
#define transferSizeBitsADC 24
#define CSPolarityIdleADC 0x0E //Chip select polarity at idle
//DAC Idle High 0x0F
//ADC Idle Low 0x0E
#define DACSPI 2
#define dspiBaudRateDAC 25000000
#define transferSizeBitsDAC 8
#define ...