Using SPI to communicate with L6470 and nRF52832

RE: Using SPI to communicate with L6470 and nRF52832

jablackann — Tue, 07 Nov 2023 14:46:23 GMT

So i am not exactly sure what is the problem but in l6470.c file for the init it had the following

#define L64X0_INIT(n)							\
	static const struct l64x0_config l64x0_cfg_##n = {		\
		.spi = SPI_DT_SPEC_INST_GET(n,				\
					    SPI_OP_MODE_MASTER |	\
					    SPI_MODE_CPOL | 		\
					    SPI_MODE_CPHA |		\
					    SPI_TRANSFER_MSB |		\
					    SPI_WORD_SET(8) |		\
					    SPI_LOCK_ON,		\
					    0),				\
	};								\
									\
	DEVICE_DT_INST_DEFINE(n,					\
			      &l64x0_init,				\
			      NULL,					\
			      NULL,					\
			      &l64x0_cfg_##n,				\
			      POST_KERNEL,				\
			      0,					\
			      NULL);

DT_INST_FOREACH_STATUS_OKAY(L64X0_INIT)

I changed it to the following:

#define L64X0_INIT(n)							\
	static const struct l64x0_config l64x0_cfg_##n = {		\
		.spi = SPI_DT_SPEC_INST_GET(n,				\
					    SPI_OP_MODE_MASTER |	\
					    SPI_MODE_CPOL | 		\
					    SPI_MODE_CPHA |		\
					    SPI_TRANSFER_MSB |		\
					    SPI_WORD_SET(8) |		\
					    SPI_LOCK_ON,		\
					    0),				\
	};								\
									\
	DEVICE_DT_INST_DEFINE(n,					\
			      &l64x0_init,				\
			      NULL,					\
			      NULL,					\
			      &l64x0_cfg_##n,				\
			      POST_KERNEL,				\
			      90,					\
			      NULL);

DT_INST_FOREACH_STATUS_OKAY(L64X0_INIT)

Changing the the parameter after POST_KERNEL from a 0 to 90. I don't know what that values represents. The code then builds and will run on the nRF52832. devzone.nordicsemi.com/.../l6470.c

RE: Using SPI to communicate with L6470 and nRF52832

helsing — Tue, 07 Nov 2023 14:39:50 GMT

Here is an SPI sample. Perhaps you could compare this one with your own one?

https://github.com/too1/ncs-spi-master-slave-example/blob/master/nrf52dk_nrf52832.overlay

RE: Using SPI to communicate with L6470 and nRF52832

jablackann — Fri, 03 Nov 2023 15:11:58 GMT

Hello,

Thanks for the suggestion. I tried switching it to the SPI2 but I don't think that worked either.

Now it reports the following

-edt-pickle C:/code/009-Nordic-projects/nrfconnect/spi_L6470_ncs_2_5_0/spi_l6470/build/zephyr/edt.pickle""
Memory region         Used Size Region Size %age Used
           FLASH:       28972 B       512 KB      5.53%
             RAM:        5900 B        64 KB      9.00%
        IDT_LIST:          0 GB         2 KB      0.00%
ERROR: /soc/spi@40023000/l6470@0 POST_KERNEL 0 108 < /soc/spi@40023000 POST_KERNEL 70 107
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\code\009-Nordic-projects\nrfconnect\spi_L6470_ncs_2_5_0\spi_l6470\build

RE: Using SPI to communicate with L6470 and nRF52832

helsing — Fri, 03 Nov 2023 14:44:06 GMT

Hello,

I will look into this after the weekend. In the meantime, you could perhaps check if changing from 'spi1' to for example 'spi2' makes any difference.