ARM32 support

[ditek]

Request to support ARM32 platform.

ARM64 was added in #118 and there are many comments on that issue about Raspberry Pi and ARM32, so I thought there should be a separate issue for that.

[githubrobinlu]

Request to support MIPS too.

[debevv]

+1 for this. I think the lack of a debugger on ARM32 is what is preventing a lot of devs from using go for embedded programming

[nikitos1550]

+1

[DominikBasnerSotec]

+1

[scalarion]

+1

[fouge]

+1

[markfarnan]

+1 Would very much like to debug directly on the RPI-32 with VSCode Remote server and Delve

[jbcoder2]

+1

[SuperFromND]

+1

[yanggeorge]

+1

[zlmink]

Bounty source

[debevv]

What are the required steps to port a new architecture?
Is the current ARM 64 code in pkg/proc/native a good starting point in this case?
I'm asking because I might try to port it in the next days

[efancier-cn]

+1 , really need it on ARM 32

[shytikov]

Would like to add my voice to army of people who really longing for ARM32 support!

[zachpanter]

+1, this would be immensely helpful.

[finferflu]

Just got a Raspberry Pi 400 and it looks like Go development will be hindered by this 😞

[davidjspooner]

I switched to the 64bit build of raspberry pi os - https://downloads.raspberrypi.org/raspios_arm64/images/ and ( with a pi4 ) am able to remotely debug just fine...

[advancedwebdeveloper]

Ping

[markoxley]

Any movement on this? Like others in this thread, I am keen to use Delve on Arm 32

[pgeiem]

We are also really interested to use Delve on Arm32. Any news regarding this ?

[adelgado0723]

I'm successfully remote debugging on a raspberry pi zero running raspbian (ARM 32) using puppywang's code https://github.com/puppywang/delve. I know issues have been brought up with this (mostly a lack of testing methodology), but it seems to work for some people.

#2122

[soypat]

I am voicing my support for this. ➕ 1️⃣ In case @puppywang hadn't seen it BountySource is at 800$

[wlanboy]

Would like to support this too.
Would allow me to debug golang nativeliy on my Raspberry Pi 400.

[efancier-cn]

The request has been here a while, anyone knows any update on this?

[agambier]

+1, would be helpful

[HM4704]

I have looked into puppywang's code and fixed some problems.
With this changes the debugger looks quite stable and I am able to debug the debugger on my Raspi.
Unfortunatly the code is still not good enough to be merged.
Here is my branch.

[parvit]

@HM4704 Hi, what exactly would be necessary to add to the branch you're pointing to?

[HM4704]

@https://github.com/parvit You can make a PR which I would merge.

[parvit]

@HM4704 I'm sorry i meant a different thing: i wish to know what kind of changes remain to implement in your branch for merging into the main.

[HM4704]

@https://github.com/parvit
It has been a while since I looked into it but here are the problems I remember:

• a lot of unit tests still fail and/or are disabled for ARM. Try to fix as many as possible.
• I have marked oode parts I was not sure what todo with "Todo" or "//??". Decide what todo there.
• one unit test especially, TestContinueMulti(), bothered me alot. I spent days to fix it but I did not succeed in the end. I stll think the problem with this test is the flushing of the cpu caches after setting/removing the software breakpoint. I tried different approaches but none worked reliably. With a hardware debugger one could perhabs seee what is going wrong there but i do not own one.
• clean up the code

[hrx619273072]

+1 for this. I think the lack of a debugger on ARM32 is what is preventing a lot of devs from using go for embedded programming

The rapid rise of edge gateways, such as the EMS I'm working on, which is built on the Cortex-A7 platform, has made traditional C language development increasingly challenging. Our system relies heavily on TCP, UDP, and MQTT protocols, while also needing to parse JSON and XML data formats and manage a substantial amount of log data. These tasks are significantly easier to handle with Go, leading us to desire a sooner migration to the Go platform for development.
Fortunately, our system's embedded web component is already developed using Go + Vue, seamlessly interacting with our existing C codebase. We eagerly await the day when DLV provides full support for ARM32, as that will be the catalyst for our migration efforts.

[Taruu]

Also as @hrx619273072 i want use Go for embedded solution with mqtt and Json. I want use Go for make update service on swupdate, and after make service api for other special functionality. I want to check what @HM4704 did, and make bug list.
If i have enough time i can try make remote stand for test on multiple arm devices. (Raspberry Pi 3b, Orange Pi R1, Orange Pi 2G-IOT, Allwinner A40i based at workplace)
And I'll try to look at the errors that need to be fix.

[agambier-iem]

As @Taruu and @hrx619273072 I'm using Go on a llinux battery powered embedded on street device. When I can I develop some packages on my laptop, debug them and cross compile them in the final target but many times I have to debug using Printf(). It would so much easier with a remote debugger.

I've been working on this project for 2 years and the next few years will be for several product based on this first embedded device.