Portsdown Buster Jetson nano

[Patrick]

hello.
just one question.
is the Portsdown Buster compatible with the Nano Jetson?
thanks for the answer.
73 ‘ S
Patrick
F6EXX

[G8GKQ]

Hi Patrick

The simple answer is no.

There is the facility to control a network-connected Jetson Nano from the Portsdown, but since I wrote that into the Portsdown code, the Jetson Nano new-build configuration has changed so it is no longer compatible.

I just don't have the time to update it all at the moment. I'm having enough trouble keeping Portsdown builds working!

73

Dave

[Patrick]

Merci

[G0LJF]

Hi Dave,

Sorry to ask a second time but I had assumed the last Buster build (I keep mine up-to-date, I am on 202007012) would remotely control a Jetson Nano and LKV373A V3 encoder?
I was reading your articles in the last few CQTV issues (265 and 268) about the recommended setup.

I also read this https://wiki.batc.org.uk/Jetson_Nano and it does say " jetson-nano-sd-r32.1-2019-03-18 image and will not work with later images". Is this image version the source of the problem? I put the very latest NV Jetson image on MD5: 5da27fe0e5f5b4d6d91dbdc1833a4ae4 (and updated Urbuntu as instructed).

So you are now saying that this is, today the 30th July, a non starter?

I have just bought a Nano (945-13450-0000-100), router, and LKV373A you see on the assumption that it was going to function as documented in CQTV.

I did have problems with the F5OEO setup script not finding many packages, but I fixed all that. Is this the problem area?

No criticism intended, I realise this takes time - I just want to know where I stand with all this brand new Jetson hardware I just bought, for the time being. Sounds like I need to hold off any testing for a while...

Thanks,

73, Mike

[G8GKQ]

Hi Mike

Yes, the issue is that NVIDIA changed some programs in the images after the one that I used for the original build, and then I moved house and lost momentum on the project. And then along came the RPi 4, and then the Ryde project, and then the Portsdown 4..... That said, I use my Nano with the old build on QO-100 regularly.

I will bump it up my priority list and let you know as soon as I have the new build working.

Dave

[G0LJF]

No probs Dave.

I always have loads to do here. What I do is order up the hardware in advance - then it is ready when I am.
The F5OEO script was failing due to seven missing packages. These were all named "libav*" such as libavcodec.
What I did was to manually install the dev versions such as libavcoded-dev.

To my simple mind this is now ready to go as the F5OEO script now runs straight through without any errors [after the -dev install fixes]?
Anyhow, I will leave it to you.

Ta,

Mike

[G0LJF]

Hi Dave,

I have connected my P2020 (latest build) up via the router model you suggested to my Jetson Nano and my LVK373A (upgraded firmware).

I have assigned fixed IP to both these two. Just as you instruct.

I have opened up Port 22 on the router to the outside world.

From my PC I can successfully SSH (putty) onto both the PI, and the Jetson no problems, but I had to do this first:


a) Activate the dormant root account on the Jetson thus "sudo passwd root". And then set a password. This is in addition to the usual user login/password I have already created when the Jetson SD card was first booted.


b) Enable root SSH password login on the Jetson by editting this "vim /etc/ssh/sshd_config". Copying a "_old" backup, using cp, as sudo first, though.

You need to remove this line

#PermitRootLogin prohibit-password

and add this (no hash)

PermitRootLogin yes



Now I can SSH from my PC to both the Jetson and the PI. And also SSH to the PI, and subsequently onto the Jetson by yet another SSH connection. For both root and my usual Jetson login.

My remaining problem is that the Buttons on the P. Jetson Config page never change from Grey to Green.
I may well have miss-typed something but then again I can SSH to and from anywhere now so I must have the right logins and IP.

Please can you suggest a next step?

73, Mike

[G8GKQ]

Mike

If your Portsdown is connected via the WAN port of the router (with the Nano and LKV373A on the LAN ports), you need to enter the Router WAN IP address into the "Jetson IP" field in the Jetson Config menu. Of course if your Portsdown is on the same LAN, you would need to enter the actual Jetson IP address.

In response to your earlier request, I have prepared an article for the next CQ-TV on how to do all this. The article is being "test driven" by some other Jetson owners before publication. I will pm you a preview copy. The method that I describe in the article avoids the need to set up an SSH-enabled root account.

Dave

[G0LJF]

Thank you Dave,

I am still persevering with this and I am ready to give my Jetson the benefit of the latest script you have kindly prepared (in draft).

But I am still perplexed by the Portsdown Jetson Config Buttons. One says "Set Jetson Root PW".

Now "root" is a special super-user account on Unix but on Urbuntu (as used on Jetson) this is deliberately disabled. So what do you use for a "Jetson Root PW"? Still puzzled.

Thanks again, 73,
Mike

[G0LJF]

Dave,

Another problem has cropped up.

I know that the default action for the TpLink router is not to acknowledge a Ping and therefore one should explicitly enable a Ping in the router configuration web page.

However, how does one revert the Lime Mini to its native Firmware version as is required?

I tried the V1.29 and then V1.30 but the Lime Report shows failures. This is an indication that the custom DVB firmware is still operational is it not?

Thanks,

Mike