What are you trying to achieve? Do you want to use the UART4 as a standard UART in order to talk to external peripherals?
If you are trying to use the linux running on the module to connect to the Cortex M debug serial, that won’t work. The serial port pins are connected to the FTDI chip on the dahlia, and only one of the processors (either Cortex-M or Cortex-A) can drive the pins at any given time.
If you have the serial mapped to the Cortex-M it won’t be accessible on linux. If you have the serial mapped on the Cortex-A the serial won’t be accessible on the RTOS.
To connect to the Cortex-M debug uart you should use your PC connected with an USB cable to the Dahlia board. You can find more information about this here:
Hi @hfranco.tx ,
Thanks for your help. I am using TorizonCore 5
I have a Verdin iMX8 Mini. I have modified the DT a few times, such as changing the UART status and adding it to the /dev directory. Today, I attempted to reinstall TorizonCore 5 and added SPI1 through modification of UART2 in the DT. However, that modification did not work for me. Could you please take a look at the DT file related to my modification?
Thank you so much for your time
the same result is here!
Verdin is the development board I use.
I modified the SPI on the DT and tested it with my component, and it worked for me before, and I reinstalled TorizonCore 5 again and made the same changes for SPI on the DT, but now I can not see it in the /dev directory.
I had an issue with the lack of a driver for LAN78XX. I needed to install TorizonCore 6, but I encountered some challenges and stopped working on it.
As a result, I decided to install TorizonCore 5, but I faced some issues after the installation process, I mean the SPIdev0.0.
really appreciate your help.
For the Cortex M4 using Dahlia and Verdin iMX8M Mini, the hello world will work by default. When you connect a USB cable to the debug port, you should see 4 USB ports in your host machine:
>> ls /dev/ | grep ttyUSB
USB3 is the linux terminal that you will use to interface with TorizonCore. USB2 is the debug port from the Cortex M4. So you can simply connect to this port (for example, by using minicom) and then run the hello world binary as described in the article.
For the SPI part, you can remove the SPIDEV by changing the imx8mm-verdin-dahlia.dtsi file or by creating an overlay that disables this node:
Thanks for the information about USB, but I would like to use UART for the terminal interface. Using USB to Serial Cable, I can see the Linux terminal on UART3, and I am sure UART 4 is for debugging the Cortex M4 and RTOS, and since we have a custom board, I want to test with UART 4 instead of USB2.
In regards to the SPI_1, I disabled it, and in the output_directory I can see the changes after checking out the DT, and after deploying it to the SOM, I still I have it in / dev/ directory.
The UART connects to the FTDI chip and then it’s converted to USB. So in this case you are already using the UART for the terminal interface. You can check the Verdin Development Board Schematics for more information:
Hi @hfranco.tx ,
Thank you so much for your time, That’s correct, I used jumpers for accessing the UARTs and I did enable the UART4 and UART2 on the DT files, but on the /dev/ I can not see the UART4 and SPI0.0.
I do not want to disable it, I need them I enable ecspi1 on the imx8mm-verdin-dahlia.dtsi and add pinctrol fo it
Could you please check the attached file to see if there is any issue with deploying images in Ubuntu? I disabled the SPI to see if it would be removed but it is still there and probably my possess has issue ubuntoutput.txt (7.0 KB)
s. If you could take a look at the text file, I would really appreciate it.
and on the Linux side I have pending for ostree status, I download the TorizonCore Long Term Supported (LTS) Releases.[ Verdin iMX8M Mini (2022-07-28 | 5.7.0+build.17.container | 202.12 MB)]