-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported architecture: armv6l #669
Comments
armv6i is not supported. |
Are there plans to add support for the armv6l architecture soon? It would be awesome if this extension worked to connect to the Pi Zero. |
Any news on this? |
awesome feature, please add Pi Zero support |
@egamma can this be added as a feature request? |
+1 would love to see Pi Zero supported. |
+1 Please add Pi Zero support. |
+1 Pi Zero support would be sooo awesome! |
+1 Please add Pi Zero support. @microsoftopensource |
Just want to mention, it is not only about Pi Zero, but other older RPis as well. Even the rPi1 is still very capable for lots of embedded use-cases, therefore still officially supported. |
I've installed the latest Raspian on RPI 3 B+ and it looks like the architecture check that takes place during the SSH connection comes back with "Unsupported architecture: armv6l". Shouldn't it be ARM V7 on this hardware? |
any news about this issue? |
@Particlemap this issue is about ARMv6, please open a separate issue with questions and issues with ARMv7. Thank you. |
+1 for ARMv6 |
+1 for ARMv6 |
+1 для ARMv6 |
+1 Please do this |
+1 ARMv6 would be great |
armv6l support would be great, even if it's just file editing and terminal |
+1 again, the community needs this is growing, and we’re about to start a revolution :D |
+1 for me as well. Simple file editing and output would be an awesome first step already |
+1 again |
+1 |
+1 for ARMv6 |
+1 for ARMv6 guys! This would be super useful for raspberry |
+1 it would be great !!! Pleas |
+1 This would be a welcome addition. |
I am waiting for arm v6 also |
I saw that DockerDesktop promises something regarding running simulator
containers. At least it is on their backlog.
…On Mon, May 4, 2020 at 12:18 AM Matt ***@***.***> wrote:
Extremely bummed to find this isn't supported on RasPi Zero W. :( I know a
lot of us would love to develop directly on the board, because we use
libraries like johnny-five and can't test locally. Having to push up to
github and pull down, or scp every time is tedious.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#669 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM7YVKB7G42EY75XYXUZ5ADRPXNS5ANCNFSM4HXTIALQ>
.
|
+1 yes please |
If you are on Linux, what you can do for now until that get's implemented is use sshfs which allows you to mount a remote file system such as the raspberry pi's one.
After that you can use your vscode to open that "pi_fs" directory and edit code there Update: |
@georgikoemdzhiev any alternatives for Windows users? |
@Misiu I updated the post above with a link to a program that seems to do the same for windows |
As @devalnor stated in the previous comments, you can use ssh fs extension in vs code, for both Linux macOS and Windows. @Misiu |
Docker Desktop provides buildx experimental feature for multiplatform development. I had never a chance to test it because Nvidia Jetson Nano is out of my home now. But it is available from Amazon. Rancher's K3s Kubernetes is the real thing and runs on Arm nodes. If they know how to do it for Kubernetes they know how to build, deploy, and debug on Arm-based boards. In Kubernetes kubectl ssh into POD is a must feature! |
If they can run Docker you can attach or ssh to the container: https://phoenixnap.com/kb/docker-on-raspberry-pi |
And they already did it: Docker for Arm |
+1 would really like to see this! is there any news? |
+1 for raspi w zero support. This is such a cheap and easy to embed device, and using vscode remote is just perfect for developing! |
May Iteration planning is over (#669). |
+1 for rpi w zero! |
+1 for rpi zero |
+1 for the armv6 support. I have few RPi 1 still kicking around |
+1 for rpi zero |
+1: 'Thankyou for being there when the world needed you most' - Satya Nadella |
+1 for RPi Zero |
+1 for |
You can use the Remote extension with that architecture. it ia just Raspberry pi Zero that is not supported yet |
Yes, you are right. I get the wrong version number of my Pi. Thanks. |
+1 for RPi Zero |
To everyone leaving comments I suggest you also thumbs up the initial comment, as I think that gets counted for priority. |
+1 |
+1 Bummed out that my Raspberry Pi 2B works fine with vscode, but my Pi Zero W is not supported at all. Any roadmap for armv6l support? |
Another +1 from me. I am trying to set up a sane non-hair-pulling process for development on a headless Raspberry Pi Zero W and the lack of support for arm6l is a major drawback. |
+1 |
Hey folks, we've definitely heard the request here and understand the interest. However, currently we are unsure that the Remote - SSH extension will realistically work with 512mb of RAM on the Pi Zero/Pi 1. While we could open up ARMv6 support, we are wary that it will not provide the experience you are really looking for from the remote extensions on those devices and we have not seen interest mentioned for other v6 devices. I'm locking this thread so that anyone coming to this issue is able to quickly see the reason why this hasn't been picked up yet (Rather than seeing a large number of +1 comments - all of which we appreciate! It's unfortunate we can't keep 👍 reactions unlocked for upvoting.) We'll provide an update here if we are able to be confident that it will work. EDIT: After some requests for clarifications, it's worth mentioning that issue here is not performance in terms of the speed that things return, but rather that the extension simply does not work well with this little RAM. Examples of issues include: frequent disconnects, files not opening, IntelliSense not starting or extensions bombing, disconnects that never return, crashing the device and/or making it unresponsive, and more. |
on a Raspberry Pi Zero W. Not sure this was ever an intended target, but I had one immediately available to test. Will attempt a Pi 2 also.
The text was updated successfully, but these errors were encountered: