apps/examples: Add path option to SPI Slave test

[eren-terzioglu]

Summary

• apps/examples: Add path option to SPI Slave test

Add path option to spislv_test example

Impact

Impact on user: Yes. Users can test different SPI slave interface just changing command
Impact on build: No.
Impact on hardware: No.
Impact on documentation: No.
Impact on security: No.
Impact on compatibility: No.

Testing

esp32c6-devkitc:spislv config used.

Building

Command to build:

make -j distclean && ./tools/configure.sh esp32c6-devkitc:spislv && make -j && make download ESPTOOL_PORT=/dev/ttyUSB0

Running

spislv -p /dev/spislv0 -x 2 abba and spislv -p /dev/spislv2 -x 2 abba commands used to test

Output

Here is the output

nsh> spislv -p /dev/spislv0 -x 2 abba
Error: Failed to open /dev/spislv0: No such file or directory
nsh> spislv -p /dev/spislv2 -x 2 abba
Slave: Queuing 2 bytes for sending to master: AB BA 

[acassis]

@eren-terzioglu why is it spislv2 instead of spislv0 ?

[cederom]

Yup, example usage mentions printf(" spislv -p /dev/spislv0\n\n"); and 0 seems to be a defalut, please update to 0 unless other reason not to use it? :-)

[eren-terzioglu]

Default path was spislv2. I did not break any workflow with this update. I can change example usage to spislv2 if it is fine for you? What do you think?

[acassis]

Yes, I noticed that, I just asked why spislv2? I suggest you trying it to understand why it was this way. It could be a typo in the original config

[eren-terzioglu]

Example creator created this to test SPI Slave for ESP32-C6. On Espressif devices we register SPI devices starting from SPI2 (because of general purpose SPI starts from SPI2) and probably he did not want to work on it much with parameter option. Only meaningfull reason comes to my mind is this.

[cederom]

Can we add the default value print to the help message? :-)

[eren-terzioglu]

Added, please take a look

[cederom]

Thank you @eren-terzioglu :-)

[acassis]

@eren-terzioglu normally other applications on NuttX let the user define the device file in the menuconfig. Please change this application to do it, then the users can change it easily

[eren-terzioglu]

@eren-terzioglu normally other applications on NuttX let the user define the device file in the menuconfig. Please change this application to do it, then the users can change it easily

We can add it but do we need to add for already parameterized example?

[acassis]

@eren-terzioglu normally other applications on NuttX let the user define the device file in the menuconfig. Please change this application to do it, then the users can change it easily

We can add it but do we need to add for already parameterized example?

I think we can use slv0 and add the default CONFIG_ to slv2 for ESP32xx board.
Probably @FelipeMdeO created this test only with ESP32 in mind, but all apps on NuttX should be generic and should work in any MCU :-)

[FelipeMdeO]

@eren-terzioglu normally other applications on NuttX let the user define the device file in the menuconfig. Please change this application to do it, then the users can change it easily

We can add it but do we need to add for already parameterized example?

I think we can use slv0 and add the default CONFIG_ to slv2 for ESP32xx board. Probably @FelipeMdeO created this test only with ESP32 in mind, but all apps on NuttX should be generic and should work in any MCU :-)

Yes, I did this implementation and tested it only in esp32 env. Maybe I did a mistake using slv2.