We intend to use QSPI_1_CLK for simple GPIO output, so I was wondering how to change the feature of this pin to GPIO. Is it listed in the device tree, and do I need to change it there? Is there a tutorial you can recommend? I found this page, but it is quite difficult for me.
When I look for ls /boot/overlays noting in this folder, [ls: cannot access ‘/boot/overlays’: No such file or directory]
QSPI_1_CLK info is below:
gpiochip2 - 32 lines:
line 0: “SODIMM_52” unused input active-high
Hi @josep.tx ,
Thank you for your response.
The page that you send is related to unpacking the image, building the image, and checking out the image. Modifying and changing one-pin behavior is not a straightforward process.
Changing the name of the node to gpio11grp actually doesn’t have any effect on the hardware functionality. The name of the node (gpio11grp) and its label (pinctrl_gpio11) are there mainly for organization purposes in this case.
The pin muxing is actually defined in the line below by the MX8MM_IOMUXC_NAND_ALE_QSPI_A_SCLK macro.
I think I found my question below
if the process is correct for the device what should I add for SPI_2 in the VS code?
I should create a Create Symbolic Links and I did make a spisample with full permission
and added the /dev/spisample to the device on the torizon configuration
but when I run the code I have an error
can’t open device: No such file or directory
Could you please let me know if there is something should I consider in the device tree?