Hi,
I do not use the SPIDEV fragment, so I've deleted it out of the Overlay.
The data sheet of the ATREB233 says that the SPI cut get up to 7.5 MHZ
but decreasing it does have no positive effects.
My SPI Configuration is specified for the BBB.
I do think that released the RX_Save_MODE means, that the frame buffer
is not any more protected, so that the hardware can override the
FrameBuffer.
I've checked the value of register 0x0c periodically but it does not
change its value while operating. But i have no idea how to make the
regmap volatile.
Best Regards
Sebastian Balz
Am 08.07.2017 um 20:14 schrieb Alexander Aring:
Hi,
On Sat, Jul 08, 2017 at 08:11:13PM +0200, Alexander Aring wrote:
Hi,
On Sat, Jul 08, 2017 at 08:06:48PM +0200, Alexander Aring wrote:
...
The Registers a configured as:
cat /sys/kernel/debug/regmap/spi1.0/registers
01: 16
02: 16
03: 00
04: 20
05: 00
06: 20
07: ff
08: 1a
09: 00
0a: 00
0b: 00
0c: a0
RX_SAFE_MODE is 1 here, good.
It could be that I misunderstood the datasheet, and the RX_SAFE_MODE is
"released" on loosing CS. Which means we need to reenable the bit after
each received frame.
maybe you could check that? :-/
one small note here, for that you need to make the register for
RX_SAFE_MODE volatile - don't trust regmap for now, because it's using
shadow register - with volatile it will not use shadow registering!
- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
