Search found 43 matches

by ephogy
Fri Jul 10, 2026 12:05 pm
Forum: NetBurner Software
Topic: Ethernet 2 on the SOMRT1061
Replies: 0
Views: 215

Ethernet 2 on the SOMRT1061

Quick question regarding the second ethernet port on the SOMRT1061 board

(Note the nomenclature difference where the DEV-SOMRT1061 indicating ENET0/ENET1, and software/SOMRT1061_pinout using ENET and ENET2)
In the schematic for the dev board, ENET1_SPEEDLED is connected to PIN_40_GPIO1_IO16
In the ...
by ephogy
Fri Jul 10, 2026 7:28 am
Forum: NetBurner Software
Topic: SOMRT1061 system crashes
Replies: 7
Views: 15120

Re: SOMRT1061 system crashes

Quick question: there is 64MB of memory on the MOD54415, and standard stack sizes are 8k to 12k. Why trim them down?
That's a good question -- Probably because this all started out on the MOD5272 and I needed the space there and I just carried it over.

Turns out the problem was not the software ...
by ephogy
Wed Jun 17, 2026 11:34 am
Forum: NetBurner Software
Topic: SOMRT1061 system crashes
Replies: 7
Views: 15120

Re: SOMRT1061 system crashes

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 ...
by ephogy
Tue Jun 16, 2026 10:45 am
Forum: NetBurner Software
Topic: SOMRT1061 system crashes
Replies: 7
Views: 15120

Re: SOMRT1061 system crashes

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 ...
by ephogy
Mon Jun 15, 2026 1:08 pm
Forum: NetBurner Software
Topic: SOMRT1061 system crashes
Replies: 7
Views: 15120

SOMRT1061 system crashes

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 ...
by ephogy
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: 46307

Re: SOMRT DSPI Driver clock phase and polarity using GPIO as CS

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 ...
by ephogy
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: 46307

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.
by ephogy
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: 46307

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 ...
by ephogy
Tue Sep 17, 2024 7:05 am
Forum: NetBurner Software
Topic: Porting code from MOD5441X to SOMRT1061
Replies: 4
Views: 65553

Re: Porting code from MOD5441X to SOMRT1061

Thanks dciliske, perfectly clear. I appreciate the explanation.
by ephogy
Mon Sep 16, 2024 9:46 am
Forum: NetBurner Software
Topic: Porting code from MOD5441X to SOMRT1061
Replies: 4
Views: 65553

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