I've opened a support ticket, but perhaps I can explain it here as well.
Part of this might be heritage related.
We use the four chip selects, and feed them into a demux to produce 16 outputs. We use this to talk to 12 SPI devices.
To operate this properly on the SOMRT1061, I can't use the chip ...
Search found 38 matches
- Tue Feb 10, 2026 11:25 am
- Forum: NetBurner Software
- Topic: SOMRT DSPI Driver clock phase and polarity using GPIO as CS
- Replies: 5
- Views: 3625
- Mon Feb 09, 2026 10:17 am
- Forum: NetBurner Software
- Topic: SOMRT DSPI Driver clock phase and polarity using GPIO as CS
- Replies: 5
- Views: 3625
Re: SOMRT DSPI Driver clock phase and polarity using GPIO as CS
Hi Tom
Sorry. This is with the most recent NNDK 3.57, SOMRT1061.
Sorry. This is with the most recent NNDK 3.57, SOMRT1061.
- Thu Feb 05, 2026 7:21 am
- Forum: NetBurner Software
- Topic: SOMRT DSPI Driver clock phase and polarity using GPIO as CS
- Replies: 5
- Views: 3625
SOMRT DSPI Driver clock phase and polarity using GPIO as CS
In the DSPI Driver, a call to Init(..) will initialize the SPI almost as expected:
spi()->CR = LPSPI_CR_RST(1); // This statement causes the SPI to reset, Clock polarity and phase are set to 0.
The function returns with clock phase/polarity in 0/0. I then have to trigger the GPIO lines ...
spi()->CR = LPSPI_CR_RST(1); // This statement causes the SPI to reset, Clock polarity and phase are set to 0.
The function returns with clock phase/polarity in 0/0. I then have to trigger the GPIO lines ...
- Tue Sep 17, 2024 7:05 am
- Forum: NetBurner Software
- Topic: Porting code from MOD5441X to SOMRT1061
- Replies: 4
- Views: 46827
Re: Porting code from MOD5441X to SOMRT1061
Thanks dciliske, perfectly clear. I appreciate the explanation.
- Mon Sep 16, 2024 9:46 am
- Forum: NetBurner Software
- Topic: Porting code from MOD5441X to SOMRT1061
- Replies: 4
- Views: 46827
Re: Porting code from MOD5441X to SOMRT1061
Hi Tom,
I understand -- on the old MOD5441X, I was already copying the memory mapped flash space to a location in RAM, so it's somewhat simple.
I'd just marked the end of the flash space as where I would store this extra data.
I was storing to an arbitrary place in flash which was significantly ...
I understand -- on the old MOD5441X, I was already copying the memory mapped flash space to a location in RAM, so it's somewhat simple.
I'd just marked the end of the flash space as where I would store this extra data.
I was storing to an arbitrary place in flash which was significantly ...
- Thu Sep 12, 2024 2:46 pm
- Forum: NetBurner Software
- Topic: Porting code from MOD5441X to SOMRT1061
- Replies: 4
- Views: 46827
Porting code from MOD5441X to SOMRT1061
I saw that the calls to FlashProgram and FlashErase were failing to compile and tracked down the Hal_StorageSave and Hal_StorageRead functions.
Hal_StorageSave on the MOD5441X seems to simply be a wrapper for FlashProgram and FlashErase which is great. Hal_StorageRead doesn't exist for the MOD5441X ...
Hal_StorageSave on the MOD5441X seems to simply be a wrapper for FlashProgram and FlashErase which is great. Hal_StorageRead doesn't exist for the MOD5441X ...
- Thu Aug 29, 2024 1:15 pm
- Forum: NetBurner Software
- Topic: 2.x to 3.x migration and updates
- Replies: 3
- Views: 34625
Re: 2.x to 3.x migration and updates
This is probably what I'm looking for. I was running through the nbupdate.cpp code and didn't see any calls before the flashing occurred. I see they are in config_server.cpp.
Thank you.
Thank you.
- Wed Aug 28, 2024 9:36 am
- Forum: NetBurner Software
- Topic: 2.x to 3.x migration and updates
- Replies: 3
- Views: 34625
2.x to 3.x migration and updates
I've been migrating some MOD5414X code from 2.x to 3.x and I was using the update_shutdown_func and the update_complete_func. I can't seem to locate similar function calls in the nbupdate.cpp file.
Am I missing something here, or are there plans to add these function callbacks? They're useful for ...
Am I missing something here, or are there plans to add these function callbacks? They're useful for ...
- Wed Jul 10, 2019 9:42 am
- Forum: NetBurner Software
- Topic: MOD54415, EFFS, DSPI, and QSPI
- Replies: 2
- Views: 5369
Re: MOD54415, EFFS, DSPI, and QSPI
So.. Looks like I don't need to use the IRQ code, but the interrupt driven code is about 15% faster, at least how I'm using it, than the non-interrupt driven code, which should (?) be faster. MicroSD card access has fairly low priority in my application so this might be why the interrupt driven ...
- Wed Jul 10, 2019 8:51 am
- Forum: NetBurner Software
- Topic: MOD54415, EFFS, DSPI, and QSPI
- Replies: 2
- Views: 5369
Re: MOD54415, EFFS, DSPI, and QSPI
I can't speak for 2.7.5 as I'm using 2.8.7, but yes? SPI0 is not brought out to J1/J2 other than CS3.
I'm not sure whether you need to enable the interrupt driver for it if you want to use SPI1-3.
Uncomment #define SD_IRQ_QSPI in MOD5441X\system\mmc_mcf.cpp if you do?
In porting my MOD5272 code to ...
I'm not sure whether you need to enable the interrupt driver for it if you want to use SPI1-3.
Uncomment #define SD_IRQ_QSPI in MOD5441X\system\mmc_mcf.cpp if you do?
In porting my MOD5272 code to ...