Re: nuttx lora sx127x device use for help
That's what it used to be, but I used two boards to execute sx127x -r on one of the boards and sx127x -t on the other, expecting communication between the two boards, but it didn't work as expected . Do you need any other configuration? the first board: nsh> sx127x -t Start sx127x_demo LORA modulation Set frequency to 93000 Set power to 14 Send 5 bytes the sencond boad: nsh> sx127x -r Start sx127x_demo LORA modulation Set frequency to 93000 Set power to 14 Waiting for data It looks like it's stuck, and the message sent is not received. Is there something wrong with my configuration? Can you help me have a look? I've been doing it for a long time and haven't done it yet.
nuttx imxrt board serial use for help
A board of our own imxrt1052, refer to nuttx/boars/arms/imxrt/imxrt1050-evk, and plan to use these serial ports /* LPUART1 */ #define GPIO_LPUART1_RX (GPIO_LPUART1_RX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B0_13 */ #define GPIO_LPUART1_TX (GPIO_LPUART1_TX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B0_12 */ /* LPUART2 */ #define GPIO_LPUART2_RX (GPIO_LPUART2_RX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_03 */ #define GPIO_LPUART2_TX (GPIO_LPUART2_TX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_02 */ /* LPUART3 */ #define GPIO_LPUART3_RX (GPIO_LPUART3_RX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_07 */ #define GPIO_LPUART3_TX (GPIO_LPUART3_TX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_06 */ /* LPUART4 */ #define GPIO_LPUART4_RX (GPIO_LPUART4_RX_1|IOMUX_UART_DEFAULT) /* GPIO_SD_B1_01 */ #define GPIO_LPUART4_TX (GPIO_LPUART4_TX_1|IOMUX_UART_DEFAULT) /* GPIO_SD_B1_00 */ /* LPUART8 */ #define GPIO_LPUART8_RX (GPIO_LPUART8_RX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_11 */ #define GPIO_LPUART8_TX (GPIO_LPUART8_TX_1|IOMUX_UART_DEFAULT) /* GPIO_AD_B1_10 */ UART1 is used as the console, but in the process of using it, it is found that if three or more serial ports are selected in the menconfig configuration, the console cannot be opened. If two serial ports are selected, the console will be opened normally. Have you encountered it?
Can musl libc replace the libc of nuttx system？
I am currently working on a project that I want to transplant musl LIC to nuttx to replace the built-in libc, have any friends done similar work? I want to ask how to start.Thank you.
How to use the w5500 network module？
I saw the driver code of the w5500 on Nuttx, but I did not find any routine
using these driver codes. The w5500_initialize interface has not been called by
any code. Have any friends used the w5500 on nuttx?
int w5500_initialize(FAR struct spi_dev_s *spi_dev,
FAR const struct w5500_lower_s *lower,
unsigned int devno)
{
FAR struct w5500_driver_s *self;
How to use the UART1-UART3 on k210
K210 can only use UART0 at present. I would like to ask my friends, who has the driver code for UART1-UART3? The current project needs to use it. It is too difficult to transplant from the official code of K210.
imxrt1176 on Nuttx
I want to ask my friends, is there anyone who supports imxrt1176 on Nuttx？At present, there are only imxrt1020, imxrt1050, imxrt1060 and imxrt1064 in the Nuttx code.
How to use the esp8266 network module？
I saw the code of esp8266 in the directory apps/netutils/esp8266, but there is no test case. How can I test esp8266 using the UART?
simulation spi driver
Have any friends done gpio simulation spi on Nuttx？
How to use spi_bitbang to drive SD card
I use spi_bitbang to drive the SD card on the k210 chip development board, referring to the content in the sam_mmcsd.c file， The following two configuration items are opened: CONFIG_SPI_BITBANG and CONFIG_MMCSD_SPI，After compiling, programming and starting, you can see /dev/mmcsd0, but when you insert the sd card and execute "mount -t vfat /dev/mmcsd0 /mnt" to mount the sd card, the following error is reported "nsh : mount: mount failed: Function not implemented".I want to ask my friends, is there a solution to this problem?
Re: How to use spi_bitbang to drive SD card
I have now turned on the debug option, started the development board and reported the following error: k210_sdinitialize: Initializing bit bang SPI for the MMC/SD slot spi_setmode: mode=0 k210_sdinitialize: Successfully initialized bit bang SPI for the MMC/SD slot k210_sdinitialize: Binding bit bang SPI device to MMC/SD slot 0 spi_lock: lock=1 spi_setmode: mode=0 spi_setmode: mode=0 exchange=0x8000f2a4 spi_setbits: nbits=8 spi_setfrequency: frequency=40 holdtime=55 actual=401445 spi_setfrequency: frequency=40 holdtime=55 actual=401445 mmcsd_mediainitialize: Send CMD0 spi_select: devid=65536 selected=1 mmcsd_sendcmd: ERROR: Failed: i=9 response=ff spi_select: devid=65536 selected=0 mmcsd_mediainitialize: Send CMD0 spi_select: devid=65536 selected=1 mmcsd_sendcmd: ERROR: Failed: i=9 response=ff spi_select: devid=65536 selected=0 mmcsd_mediainitialize: ERROR: Send CMD0 failed: R1= spi_select: devid=65536 selected=0 spi_lock: lock=0 spi_lock: lock=0 k210_sdinitialize: Successfully bound bit bang SPI device to MMC/SD slot 0 I created a new k210_mmcsd.c file with reference to the sam_mmcsd.c file, defined the spi_select, spi_status, and spi_cmddata functions in the file, and defined the k210_mmcsd_spiinitialize function to configure and initialize GPIO, and finally defined the k210_sdinitialize function, and called k210_sdinitialize in the k210_bringup function.
