NetBurner Community Forum

Thanks for these detailed responses. I'm thinking it is a memory issue somewhere and I'm attempting to track it down.
To answer your questions,
Stack sizes are custom -- I'd trimmed them down on the MOD5441X code. Once things started going wonky, I set them back to the standard stack sizes.

I don't ...

Increasing the Ethernet stack just simply increased the time it took to cause an error

With TaskScan, I noticed one of my tasks was reporting only 800 bytes free of 16kB on the SOMRT1061 vs the MOD5441X unit reporting 15436 bytes free.

The function has a switch statement in it with some scoped ...

I've made a break out board for the SOMRT1061 so that I can use it as a drop in replacement for systems using the MOD5441X board.

I'm using the same code base to compile for the MOD5441X board under the 2.9.7 kernel and compiling for the SOMRT1061 under the 3.5.7 kernel.

Both system run, but the ...

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 ...

Hi Tom
Sorry. This is with the most recent NNDK 3.57, SOMRT1061.

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 ...

Thanks dciliske, perfectly clear. I appreciate the explanation.

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 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 ...

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.