search

rt-net / JetsonNano_DT_SPI

SPI1 enabled DTS and flash-tools for Jetson Nano
GNU General Public License v2.0
28 stars 9 forks source link

No graphical interface after reboot #4

Closed ADV-LUT closed 5 years ago

ADV-LUT commented 5 years ago

Hi @Tiryoh ,

thanks for the helpful script. Unfortunately I do not get a graphical user interface during the reboot. But I can access and use the board via ssh. Any suggestion why it is so?

Tiryoh commented 5 years ago

Hi @ADV-LUT ,

Thanks for your report. I've never faced that issue. The dmesg command shows the kernel log, so I think you can find something helpful. Could you tell me your L4T version, which can check by head -n 1 /etc/nv_tegra_releas?

ADV-LUT commented 5 years ago

Hi,

I found my issue, you have used a older version. When I used the older SD-Card image from the 18.03.2019 your script works well.

What do I have to do if I want to use the new L4T version from 16.07.2019?

I want to use the SPI to enable CAN communication on the nano. I would like to use an MCP2515 CAN interface with an MCP2562 transceiver.

How do I have to change the kernel and scripts? Do you have any tips for me?

Thanks for your help and your great work.

Tiryoh commented 5 years ago

Hi @ADV-LUT,

Thanks for your feedback.

What do I have to do if I want to use the new L4T version from 16.07.2019?

Unfortunately, I don't know what to do at this point. I have only tested on the version on R32.1.0 which was published in March 2019. I'll test and modify the script soon to make L4T version R32.2.0 which was published in July 2019.

How do I have to change the kernel and scripts? Do you have any tips for me?

At this point, there is only a way I can guide you is to use the older version image, L4T R32.1. I think L4T R32.1 and rt-net/JetsonNano_DT_SPI makes the SPI device MCP2515 available to access via Pin 19, 21, 23 and 24 on Developer Kit. The J41 Header Pinout is available here: https://www.jetsonhacks.com/nvidia-jetson-nano-j41-header-pinout/.

ADV-LUT commented 5 years ago

Hi @Tiryoh,

thanks for the great feedback.

I connected the MCP2515 correctly and decided to use Pin22 (GPIO13) as an interrupt pin. However, I do not know now how to continue. I also find no documents, how I have to configure it for a Nano or generally in a Linux system.

I know this is a little bit away from the current problem, but I would very grateful for help.

Where do I have to activate or register the MCP2515 in the kernel? Where do I define that the pins are the MCP2515 and CAN and where stands the ćhoosen interrupt pin??

I found this: https://www.jetsonhacks.com/2017/04/04/gpio-and-spi-nvidia-jetson-tx1/

But I do not understand how now my next step, if I use your script and the nano.

Tiryoh commented 5 years ago

Hi @ADV-LUT,

I connected the MCP2515 correctly and decided to use Pin22 (GPIO13) as an interrupt pin.

There are 2 SPI functions for Jetson Nano DK.

The target of this tool is to enable SPI0 on Linux, SPI1 on DK. Therefore, we can only use Pin 19, 21, 23 and 24 on Developer Kit. Pin 13, 16, 18, 22 and 37 are only available for SPI1 on Linux, SPI2 on DK.

Where do I have to activate or register the MCP2515 in the kernel? Where do I define that the pins are the MCP2515 and CAN and where stands the ćhoosen interrupt pin??

I read https://www.jetsonhacks.com/2017/04/04/gpio-and-spi-nvidia-jetson-tx1/, it seems to rebuild the kernel. At this point, I'm not sure how to rebuild the kernel successfully.

Tiryoh commented 5 years ago

This issue will be closed because there is no update for a while. Please feel free to re-open this issue if you have any problems again.