开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

An alternative for sBitx software development


 

Visual Studio (VS) code has a Microsoft extension, Remote-SSH, that allows you to run VS Code on one computer and do the software development on another over SSH. This works with the Raspberry Pi (sBitx) as the remote computer. This allows you to run VS Code on a more powerful computer with a larger screen (without having to connect a HDMI display to the sBitx.

This creates an environment where I edit the code on my PC or Mac (where I have a 4K monitor), but still build and run it on the sBitx. Intellisense code highlighting and git version control work, including integration to my repo on GitHub.

--
73,
Mark, N8ME


 

I do that my ssh-ing to the rpi. It doesn't work as well as the VS I guess but I open two sessions: one to edit and one to debug.
- f

On Fri, Oct 20, 2023, 2:44 AM Mark Erbaugh <mark.election@...> wrote:
Visual Studio (VS) code has a Microsoft extension, Remote-SSH, that allows you to run VS Code on one computer and do the software development on another over SSH. This works with the Raspberry Pi (sBitx) as the remote computer. This allows you to run VS Code on a more powerful computer with a larger screen (without having to connect a HDMI display to the sBitx.

This creates an environment where I edit the code on my PC or Mac (where I have a 4K monitor), but still build and run it on the sBitx. Intellisense code highlighting and git version control work, including integration to my repo on GitHub.

--
73,
Mark, N8ME


 

What editor do you use? I assume it is running on the RPi.

--
73,
Mark, N8ME


 

I found another advantage to running VS Code on my PC with a large monitor. I was working on my modified version of the sBitx code which wasn't working as well as the stock version. I opened file from the stock firmware in a window side by side with my version to compare them. I also cut and pasted some code from the stock version into my code.
--
73,
Mark, N8ME


 

I have trained myself to love vi. It is a single lightweight editor that is available on every platform from linux to android.
It is has a little bit of learning curve of an hour, but you get used to it pretty quickly.
- f

On Fri, Oct 20, 2023, 4:40 PM Mark Erbaugh <mark.election@...> wrote:
I found another advantage to running VS Code on my PC with a large monitor. I was working on my modified version of the sBitx code which wasn't working as well as the stock version. I opened file from the stock firmware in a window side by side with my version to compare them. I also cut and pasted some code from the stock version into my code.
--
73,
Mark, N8ME


 

I am also using VS Code with the git, remote-ssh, and C language extensions. Works great.?


 

On Fri, Oct 20, 2023 at 11:07 AM, Ashhar Farhan wrote:
I have trained myself to love vi.
On Sun, Oct 22, 2023 at 09:39 AM, Stefan Beck wrote:
I am also using VS Code with the git, remote-ssh, and C language extensions. Works great.?
VS Code also has a 'vim' extension so you can use vi keystrokes to drive its editor.

Just sayin'...

?
--
Regards,
Dave, N1AI


 

Dave, I will move over to vs as well. It really doesnt matter to dev as we will be working off a cmake file.


On Sun, Dec 24, 2023, 10:50 AM Dave, N1AI <n1ai@...> wrote:
On Fri, Oct 20, 2023 at 11:07 AM, Ashhar Farhan wrote:
I have trained myself to love vi.
On Sun, Oct 22, 2023 at 09:39 AM, Stefan Beck wrote:
I am also using VS Code with the git, remote-ssh, and C language extensions. Works great.?
VS Code also has a 'vim' extension so you can use vi keystrokes to drive its editor.

Just sayin'...

?
--
Regards,
Dave, N1AI


 

On Sun, Dec 24, 2023 at 06:28 AM, Ashhar Farhan wrote:
Dave, I will move over to vs as well. It really doesnt matter to dev as we will be working off a cmake file.

I like vscode because of its nice integration with Git.? It makes it so you do not need to remember all those git commands.??

It also has strong cmake integration, although in my case there are still some differences in settings that it is using versus just running cmake on the command line that I need to figure out.

I also like it because it can be driven using the vim extension, although its emulation of vim has some limitations.??

It's debugger too has some limitations.? I could not figure out how to break it out of running the program so I could examine its state. You can issue gdb commands by using "-exec" at the debugger tab of the console area.? In Linux you can just hit Ctrl-C to get back to gdb.? Some pages suggested Ctrl-Shit-C would do this on vscode, but it didn't work for me.? What did work was opening a terminal window and issuing the command:

$ kill -INT `pidof sbitx`

Once I did this, I could then use "-exec" to enter gdb commands in vscode.? This works but it'd be nice to be able to enter Ctrl-C in a single keystroke.

I do need to set up the remote-ssh extension.? As was said above, vscode itself uses up a lot of resources so it's best to not run it all on the sbitx especially if you want to study performance.? I hope that I will find that it is better to run it on a fast desktop or laptop then just use the remote-ssh extension so it can access the Pi when needed.

As a side comment, I am using Pi 5 with Bookworm for other projects now, but am finding its OS to be annoying.? The use of Wayland instead of X has changed some behaviors that are part of my muscle memory and have been for decades now.? ?Apparently getting it to do "focus follows mouse" instead of "click to focus" takes you off into the world of various add-ons, and I didn't make the effort to do so.? ?Even menu item selection works differently enough for me to need to retrain myself.? Therefore I'm in no hurry to get onto Bookworm (Debian 12).? Bullseye (Debian 11) has none of these problems.? The Pi 5 though is much faster, it can decode eight FT8 streams at once with around 33% CPU remaining whereas the Pi 4 was hitting 100% CPU with four FT8 streams.? ?Therefore I keep the Pi 5 doing the number crunching and don't bother with attaching a display, I just ssh into it if/when needed.

--
Regards,
Dave, N1AI


 

Hi Dave,

I have switched one of my RPi4s to Bookworm.? You can go into the command line Raspberry Pi configuration (sudo raspi-config) and select X or Wayland as the interface.? It is in the Advanced Options.

Once I did that, I did not see much difference with Bookworm.? I am getting ready for the RPi 5 that I have on order.

73
Evan
AC9TU


 

On Sun, Dec 24, 2023 at 01:52 PM, Evan Hand wrote:
I have switched one of my RPi4s to Bookworm.? You can go into the command line Raspberry Pi configuration (sudo raspi-config) and select X or Wayland as the interface.? It is in the Advanced Options.

Once I did that, I did not see much difference with Bookworm.
I am finally playing with Bookworm (on Pi 4) and this tip was very helpful, so thank you very much.

One other observation was that the various screenshot/print-screen mechanisms were broken when using Wayland, switching back to X made things work the way they used to.? In particular I find the gnome-screenshot package to be worth installing and using under X.
?
--
Regards,
Dave, N1AI


 

On Sun, Dec 24, 2023 at 06:28 AM, Ashhar Farhan wrote:
Dave, I will move over to vs as well. It really doesnt matter to dev as we will be working off a cmake file.
I see you closed the cmake PR.? I also chose not to use that particular approach to using cmake.? If you look at the dev_main branch in the n1ai sbitx-mainline repo on github you can see the commits I cherry-picked to get a nice vscode setup with cmake.? They pretty much all come from other contributors here on groups.io?via their github repos, with a few small tweaks by me.? I might even send a PR that aggregates them if you agree to review it in a timely fashion.? ?

--
Regards,
Dave, N1AI


 

Dave,
From now on, I will clear the PRs. I am also looking for volunteers to co manage the merges with me. I am meeting mike papp tomorroe morning to put a system in place to quickly move the dev forward.
- f

On Sat, Jan 20, 2024, 10:05 PM Dave, N1AI <n1ai@...> wrote:
On Sun, Dec 24, 2023 at 06:28 AM, Ashhar Farhan wrote:
Dave, I will move over to vs as well. It really doesnt matter to dev as we will be working off a cmake file.
I see you closed the cmake PR.? I also chose not to use that particular approach to using cmake.? If you look at the dev_main branch in the n1ai sbitx-mainline repo on github you can see the commits I cherry-picked to get a nice vscode setup with cmake.? They pretty much all come from other contributors here on ?via their github repos, with a few small tweaks by me.? I might even send a PR that aggregates them if you agree to review it in a timely fashion.? ?

--
Regards,
Dave, N1AI


 

On Sat, Jan 20, 2024 at 11:47 AM, Ashhar Farhan wrote:
From now on, I will clear the PRs. I am also looking for volunteers to co manage the merges with me. I am meeting mike papp tomorroe morning to put a system in place to quickly move the dev forward.
Thanks, that is encouraging news!
?
--
Regards,
Dave, N1AI


 

Ashar,

Clearing the PRs is good. was watching Mark Erbaugh's github as he seemed to be workng his way through a lot of the siignal processing code and cleaning things up a bit. But, he never made any pull requests so you didn't geet any of those. t seems too bad to not try to include some of that work!

His repo is at

On Sat, Jan 20, 2024 at 11:47 AM, Ashhar Farhan wrote:

Dave,
From now on, I will clear the PRs. I am also looking for volunteers to co
manage the merges with me. I am meeting mike papp tomorroe morning to put a
system in place to quickly move the dev forward.
- f
--
Mike KB2ML