Как написать esp для rust - Правописание и грамматика

This is not a support channel. It's a social chat room for goofing around.

		UnKnoWnCheaTs — Multiplayer Game Hacking and Cheats First-Person Shooters Rust
[Coding] How to make a basic Proxy ESP


	Save

Authenticator Code

Page 1 of 4

Thread Tools

How to make a basic Proxy ESP

Old
4th October 2017, 06:35 AM

dorfmidge

Red Fish, Blue Fish, «blowfish», «twofish»

Join Date: Aug 2014

Location: namespace

Posts: 60

Reputation: 2624

Rep Power: 210

Recognitions

Donator

(9)

Points: 9,004, Level: 11

Level up: 28%, 796 Points needed

Activity: 1.7%

Last Achievements

How to make a basic Proxy ESP

THIS IS OUTDATED!
THIS IS OUTDATED!
THIS IS OUTDATED!
THIS IS OUTDATED!

In this thread I am going to show you how to make a basic proxy ESP using rust interceptor
This has copypasta protection! just so you know

You should edit rustinterceptor if you want to make a complex cheat there is so much more you can do if you edit it look below

This is Funny LOL

Some Credit
SunFlares — Worldtoscreen Method from his Rust Destroyer

orogamo — ProxySystem RustInterceptor (Fuckin sweeeet idea)
RustInterceptor Or you can get it right from the GitHub GitHub

First you need to download RustInterceptor Or you can get it right from the GitHub GitHub
IF YOU DONT KNOW HOW RUST INTERCEPTOR WORKS VISIT IT’S UC THREAD

After you download Rust Packet Interceptor you need to compile it to a library so we can use it our project.

Some issues you might incur while trying to compile this

You need to import some libs from rust itself like the unityengine.dll, rust.data.dll, and raknet.dll these are all found (RustClient_DataManaged) except for raknet that is found (RustClient_DataPlugins) To make it even easier for some noobs I have uploaded them in a zip.

Another issue you might have even when you import all the libs
«Interop type ‘ClientReady’ cannot be embedded. Use the applicable interface instead»

This is simple

you need to change the property «embed interop types» to false. See below for more information.

Some code changes are as follows

Code:

//In SimpleInterceptor.cs add this var
public bool connected = false;

Code:

//In the switch case replace the entities case with
 case Packet.Rust.Entities:
ProtoBuf.Entity entityInfo;
uint num = Data.Entity.ParseEntity(packet, out entityInfo);
entity = Entity.CreateOrUpdate(num, entityInfo);
if (!connected){connected = true;}
 return;

Some Big Code Changes

Code:

//In Entity.cs add this to the top
public bool IsNPC { get { return proto.baseNPC != null; } }
public bool IsEnvrecouse { get { if (Data.baseNetworkable.prefabID != null) { if ((GetName(Data.baseNetworkable.prefabID)) != null) { return proto.baseEntity != null && (GetName(Data.baseNetworkable.prefabID)).ToLower().Contains("collectable"); } else return false; } else return false; } }

Code:

//Add this somewhere in Entity.cs
public static List<Entity> Getenvrecouses()
{
return Find(item => { return item.Value.IsEnvrecouse; });
}

public static List<Entity> GetPlants()
{
return Find(item => { return item.Value.IsPlant; });
}

Now we can compile our interceptor

Now that we have got our libs compiled we can move on to the next step in making our

ESP.
Add some references! we are going to copy the contents of rust interceptor debug folder or wherever you compiled it to, to the debug folder of our winform if you don’t have a debug folder yet build your winform. Now we can add «RustInterceptor.dll» to our references YOU NEED TO KEEP THE OTHER LIBS(.dlls) IN THE SAME DIRECTORY.
Create a new project name it whatever you want for this instance we are using a WinForm project. Even though you can make this ESP in a console application.

Once you have made your new project we are going to go right to

handling our data from the proxy so make a new class called Motor.cs

Code:

public bool inserver;
public RustInterceptor Rinterceptor;
SimpleInterceptor interceptor = null;

public void start(String IP, int port)
{
interceptor = new SimpleInterceptor(IP, port);
Rinterceptor = interceptor.Interceptor;
}

public bool Connected()
{
return interceptor.connected;
}

Now lets go on and add some checkboxes or toggle whatever you want to enable/disable features to our winform. After you make these controls change all of their modifiers to public so we can access them from our overlay form.

Now lets get on with making our overlay form this requires dxsharp I will upload the libs for you. So make a new form called

[email protected] or something it doesn’t matter and download the libs for dxsharp add them all as references. In the overlay class we need to edit its instance function so edit as foll

Add a panel to your overlay form and dock it to full

Code:

//These are designer properties you need to set the properties of your form to match
this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.None;
this.BackColor = System.Drawing.Color.Black;
this.ClientSize = new System.Drawing.Size(284, 262);
this.DoubleBuffered = true;
this.ForeColor = System.Drawing.SystemColors.ControlText;
this.FormBorderStyle = System.Windows.Forms.FormBorderStyle.None;
this.Name = "Overlay";
this.Text = "Form1";
this.TopMost = true;
this.TransparencyKey = System.Drawing.Color.Black;
this.WindowState = System.Windows.Forms.FormWindowState.Maximized;
this.FormClosing += new System.Windows.Forms.FormClosingEventHandler(this.Overlay_FormClosing);
this.Load += new System.EventHandler(this.Form1_Load);
this.ResumeLayout(false);

Code:

//add these to the top
private Engine eng;
private Form1 main;
private WindowRenderTarget device;
private HwndRenderTargetProperties renderProperties;
private SolidColorBrush solidColorBrush;
private Thread sDX = null;
private float Fov = 1337f; //SET YOUR OWN RUST FOV HERE*************
private Factory factory;
private IntPtr handle;
private string fontFamily = "Arial";
private float fontSize = 10.0f;
private float fontSizeSmall = 8.0f;
private TextFormat font, fontSmall;
private FontFactory fontFactory;

// we have to add these unmanaged lib for the overlay
[DllImport("user32.dll")]
static extern bool SetLayeredWindowAttributes(IntPtr hwnd, uint crKey, byte bAlpha, uint dwFlags);

[DllImport("user32.dll")]
public static extern int SetWindowLong(IntPtr hWnd, int nIndex, int dwNewLong);

[DllImport("user32.dll", SetLastError = true)]
public static extern int GetWindowLong(IntPtr hWnd, int nIndex);

[DllImport("dwmapi.dll")]
public static extern void DwmExtendFrameIntoClientArea(IntPtr hWnd, ref int[] pMargins);

[DllImport("user32.dll")]
[return: MarshalAs(UnmanagedType.Bool)]
public static extern bool SetWindowPos(IntPtr hWnd, IntPtr hWndInsertAfter, int X, int Y, int cx, int cy, uint uFlags);

// add these vars for the overlay
public const UInt32 SWP_NOSIZE = 0x0001;
public const UInt32 SWP_NOMOVE = 0x0002;
public const UInt32 TOPMOST_FLAGS = SWP_NOMOVE | SWP_NOSIZE;
public static IntPtr HWND_TOPMOST = new IntPtr(-1);

// edit the overlay method to this
 public Overlay(Engine engs, Form1 frm)
{
main = frm;
eng = engs;
this.handle = Handle;
int initialStyle = GetWindowLong(this.Handle, -20);
SetWindowLong(this.Handle, -20, initialStyle | 0x80000 | 0x20);
SetWindowPos(this.Handle, HWND_TOPMOST, 0, 0, 0, 0, TOPMOST_FLAGS);
OnResize(null);

InitializeComponent();
}

LOL im not just gonna let you copypasta all at once

Code:

//make a formload event
private void Form1_Load(object sender, EventArgs e)
{
Width = 1337; 
Height = 7331;  
this.DoubleBuffered = true;
this.SetStyle(ControlStyles.OptimizedDoubleBuffer |// this reduce the flicker
ControlStyles.AllPaintingInWmPaint |
ControlStyles.DoubleBuffer |
ControlStyles.UserPaint |
ControlStyles.Opaque |
ControlStyles.ResizeRedraw |
ControlStyles.SupportsTransparentBackColor, true);
this.TopMost = true;
this.TopMost = false;
this.Visible = true;
factory = new Factory();
fontFactory = new FontFactory();
renderProperties = new HwndRenderTargetProperties()
{
Hwnd = this.Handle,
PixelSize = new Size2(Width, Height),
PresentOptions = PresentOptions.Immediately
};
device = new WindowRenderTarget(factory, new RenderTargetProperties(new PixelFormat(Format.B8G8R8A8_UNorm, AlphaMode.Premultiplied)), renderProperties);
solidColorBrush = new SolidColorBrush(device, Color.White);
solidColorBrush = null;
font = new TextFormat(fontFactory, fontFamily, fontSize);
fontSmall = new TextFormat(fontFactory, fontFamily, fontSizeSmall);
sDX = new Thread(new ParameterizedThreadStart(sDXThread));
sDX.Priority = ThreadPriority.Highest;
sDX.IsBackground = true;
sDX.Start();
}

Code:

//Now we need to override the onpaint event
protected override void OnPaint(PaintEventArgs e)
{
int[] marg = new int[] { 0, 0, Width, Height };
marg = null;
DwmExtendFrameIntoClientArea(this.Handle, ref marg);
}

Lets add some draw logic

Code:

 private UnityEngine.Vector2 DrawBox(int X, int Y, double Dist, SharpDX.Color color)
        {
            solidColorBrush.Color = (Color4)color;
            SharpDX.Rectangle Box = new SharpDX.Rectangle();
            Box.Width = (int)(main.BoxSize.Value / Dist);
            Box.Height = (int)(main.BoxSize.Value / Dist);
            Box.X = X - (Box.Width / 2);
            Box.Y = Y - (Box.Height / 2);
            device.DrawRectangle(Box, solidColorBrush);
            return new UnityEngine.Vector2(Box.X, (Box.Y + Box.Height));
        }

private void DrawText(int X, int Y, string text, SharpDX.Color color, float size)
{
solidColorBrush.Color = (Color4)color;
device.DrawText(text, font, new SharpDX.RectangleF((float)X, (float)Y, size * (float)text.Length, size), (SharpDX.Direct2D1.Brush)solidColorBrush);
}

Okay now we need to get our helpers created so lets make a new class called Helpers.cs

Code:

//OurWorld2Screen

public static bool WorldToScreen2(UnityEngine.Vector3 from, UnityEngine.Vector3 rot, float fovDegree, UnityEngine.Vector3 Offset, UnityEngine.Vector3 target, Rect bounds, out UnityEngine.Vector2 vector)
        {
            Stopwatch stopwatch = Stopwatch.StartNew();
            float num1 = DegToRad(fovDegree);
            float num2 = (float)((double)bounds.height / 2.0 / Math.Tan((double)num1 / 2.0));
            UnityEngine.Vector3 vector3_1 = new UnityEngine.Vector3(from.x, from.y, -from.z) + Offset;
            UnityEngine.Vector3 vector3_2 = new UnityEngine.Vector3(target.x, target.y, -target.z) - vector3_1;
            if ((double)rot.x < -180.0)
                rot.x += 360f;
            if ((double)rot.x > 180.0)
                rot.x -= 360f;
            rot = new UnityEngine.Vector3 (DegToRad(rot.x), DegToRad(rot.y), DegToRad(rot.z));
            float num3 = (float)Math.Cos((double)rot.x);
            float num4 = (float)Math.Cos((double)rot.y);
            float num5 = (float)Math.Cos((double)rot.z);
            float num6 = (float)Math.Sin((double)rot.x);
            float num7 = (float)Math.Sin((double)rot.y);
            float num8 = (float)Math.Sin((double)rot.z);
            float[,] numArray = new float[3, 3]
            {
        {
          (float) ((double) num5 * (double) num4 - (double) num8 * (double) num6 * (double) num7),
          (float) (-(double) num3 * (double) num8),
          (float) ((double) num5 * (double) num7 + (double) num4 * (double) num8 * (double) num6)
        },
        {
          (float) ((double) num4 * (double) num8 + (double) num5 * (double) num6 * (double) num7),
          (float) ((double) num5 * (double) num3),
          (float) ((double) num8 * (double) num7 - (double) num5 * (double) num4 * (double) num6)
        },
        {
          (float) (-(double) num3 * (double) num7),
          num6,
          (float) ((double) num3 * (double) num4)
        }
            };
            vector3_2 = new UnityEngine.Vector3((float)((double)numArray[0, 0] * (double)vector3_2.x + (double)numArray[0, 1] * (double)vector3_2.y + (double)numArray[0, 2] * (double)vector3_2.z), (float)((double)numArray[1, 0] * (double)vector3_2.x + (double)numArray[1, 1] * (double)vector3_2.y + (double)numArray[1, 2] * (double)vector3_2.z), -(float)((double)numArray[2, 0] * (double)vector3_2.x + (double)numArray[2, 1] * (double)vector3_2.y + (double)numArray[2, 2] * (double)vector3_2.z));
            if ((double)vector3_2.z < 0.0)
            {
                vector = UnityEngine.Vector2.zero;
                return false;
            }
            float x = (float)((double)num2 * (double)vector3_2.x / (double)vector3_2.z + (double)bounds.width / 2.0);
            float y = (float)((double)num2 * -(double)vector3_2.y / (double)vector3_2.z + (double)bounds.height / 2.0);
            vector = new UnityEngine.Vector2(x, y);
            stopwatch.Stop();
            long elapsedMilliseconds = stopwatch.ElapsedMilliseconds;
            return true;
        }
//Credits for that function go to RUST DESTROYER i decompiled it lol I'm not going to give you mine and publicizes sigs from my private sorry :/  
//RUST DESTROYER is a thread on UC!!!!

Code:

//Sum Distance shit **P** FUCKIN DISTANCE FORMULA
public static double Distance(Vector3 ppos, Vector3 pos)
{
Double Sqr1 = Math.Pow((ppos.x - pos.x), 2);
Double Sqr2 = Math.Pow((ppos.y - pos.y), 2);
Double Sqr3 = Math.Pow((ppos.z - pos.z), 2);
return Math.Round(Math.Sqrt(Sqr1 + Sqr2 + Sqr3), 2);
}

Code:

//Some conversion 
public static float DegToRad(float deg)
{
return deg * (float)(Math.PI / 180.0f);
}

Code:

//Sum more P conversions
public static UnityEngine.Vector3 ToVector(UnityEngine.Vector3 rotator)
{
float num1 = rotator.x * 9.58738E-05f;
float num2 = rotator.y * 9.58738E-05f;
float num3 = rotator.z * 9.58738E-05f;
float num4 = (float)Math.Cos((double)num1);
float z = (float)Math.Sin((double)num1);
float num5 = (float)Math.Cos((double)num2);
float num6 = (float)Math.Sin((double)num2);
return new UnityEngine.Vector3(num4 * num5, num4 * num6, z);
}

So now we need to be able to get our entities from the motor that way we know what we are displaying

Code:

//Add sum methods to our worker/motor class

public List<Entity> GetEnvResources()
{
return Entity.Getenvrecouses();
}

public List<Entity> GetPlants()
{
return Entity.GetPlants();
}

Now so we can get the prefab name of the entity we are going to add a method to our motor I’m going to leave parsing the name up to you

Code:

  public String IdToString(uint id)
        {
//this will return somthing like "assets/bundled/prefabs/autospawn/collectable/stone/metal-collectable.prefab"
            String name = Entity.GetName(id);
            if (name != null)
                 return name ;
            return "";
        }

Alright now that we have the bases down for our class we need to create the main thread that will handle our drawing and update each frame

Code:

 private void sDXThread(object sender)
{
    while (true)
    {            
      device.BeginDraw();
      device.Clear(Color.Transparent);
      DrawText(0, 0, "Some Splash Text? 1337 [email protected]", Color.Orange, 15f);
         if(eng.Connected())
            {
               Entity LocalPlayer = eng.getlocal();
               List<Entity> Players = eng.getPlayers();
               //Here we will do a player ESP
               foreach (Entity Person in Players)
               {
                        UnityEngine.Vector2 vector;
                        double dist = Helpers.Distance(LocalPlayer.Position, Person.Position);
                         if (Person.Data.basePlayer.modelState.sleeping && dist < 100 && Person != LocalPlayer && main.sleepers.Checked)
                        {
                            if (Helpers.WorldToScreen2(LocalPlayer.Position, LookDir, Fov, new UnityEngine.Vector3(0.0f, 1.5f, 0.0f), Person.Position, new UnityEngine.Rect(0.0f, 0.0f, (float)this.Width, (float)this.Height), out vector))
                            {
                                DrawText((int)vector.x, (int)vector.y, Person.Data.basePlayer.name, Color.DarkBlue, fontSize);
                            }
                        }
                        else if (!Person.Data.basePlayer.modelState.sleeping && dist < 200 && Person != LocalPlayer && main.people.Checked)
                        {
                            if (Helpers.WorldToScreen2(LocalPlayer.Position, LookDir, Fov, new UnityEngine.Vector3(0.0f, 1.5f, 0.0f), Person.Position, new UnityEngine.Rect(0.0f, 0.0f, (float)this.Width, (float)this.Height), out vector))
                            {
                                Color C = Color.LightYellow;
                                DrawText((int)vector.x, (int)vector.y, Person.Data.basePlayer.name, C, fontSize);
                                Entity Held = eng.GetEnt(Person.Data.basePlayer.heldEntity);
                                DrawText((int)vector.x, (int)vector.y + 20, dist.ToString(), C, fontSize);
                            }
                        }
                }
             //end of player esp

             
              if (main.envrecourses.Checked)//This is why i said to make your control public
                    {
                        foreach (Entity Rec in eng.GetEnvResources())
                        {
                            UnityEngine.Vector2 vector;
                            double dist = Helpers.Distance(LocalPlayer.Position, Rec.Position);
                            if (dist < 80)
                            {
                                if (Helpers.WorldToScreen2(LocalPlayer.Position, LookDir, Fov, new UnityEngine.Vector3(0.0f, 1.5f, 0.0f), Rec.Position, new UnityEngine.Rect(0.0f, 0.0f, (float)this.Width, (float)this.Height), out vector))
                                {
                                    Color C = Color.Azure;
                                    string name = eng.IdToString(Rec.Data.baseNetworkable.prefabID);
                                    vector = DrawBox((int)vector.x, (int)vector.y, dist, C);
                                    DrawText((int)vector.x, (int)vector.y, name, C, fontSize);
                                    DrawText((int)vector.x, (int)vector.y + 10, dist.ToString(), C, fontSize);
                                }
                            }
                        }
                    }


                  if (main.Plants.Checked)//This is why i said to make your control public
                    {
                        foreach (Entity Rec in eng.GetPlants())
                        {
                            UnityEngine.Vector2 vector;
                            double dist = Helpers.Distance(LocalPlayer.Position, Rec.Position);
                            if (dist < 100)
                            {
                                if (Helpers.WorldToScreen2(LocalPlayer.Position, LookDir, Fov, new UnityEngine.Vector3(0.0f, 1.5f, 0.0f), Rec.Position, new UnityEngine.Rect(0.0f, 0.0f, (float)this.Width, (float)this.Height), out vector))
                                {
                                    Color C = Color.Green;
                                    string name = eng.IdToString(Rec.Data.baseNetworkable.prefabID);
                                    vector = DrawBox((int)vector.x, (int)vector.y, dist, C);
                                    DrawText((int)vector.x, (int)vector.y, name, C, fontSize);
                                    DrawText((int)vector.x, (int)vector.y + 10, dist.ToString(), C, fontSize);
                                }
                            }
                        }
                    }              
    }
}

Now we have to run the overlay from the mainform. So in your mainform add this code This also contains the thread to start the motor IP is a textbox on the main thread and so is port you should make something similar to get user input for the server ip and port.

Code:

Thread t = new Thread(delegate () 
{                
eng.start(ip.Text, int.Parse(port.Text));
});
t.IsBackground = true;
t.Priority = ThreadPriority.Highest;
 t.Start();
Thread dx = new Thread(delegate ()
{
DX = new Overlay(eng, this);
DX.ShowDialog();
 });
dx.IsBackground = true;
dx.Start();

Now you should be all set to compile and run

If you incur ANY issues please let me know as this is my first info thread and I might have missed some things and because of that this thread is subject to updates

SHA256: A3A5FE262EA5E985DC7EEE4298F4B4293779C34B8CD2E471A701F95B0710CC63 — Uploads/dxsharp/SharpDX.Direct2D1.dll
SHA256: 97CC9005F58BBBF898EABBADFAF45A994190F7088AD353648CB719D9F9313CBB — Uploads/dxsharp/SharpDX.dll
SHA256: 1F574BE760ECA0A59D43DF68BE0BF0C119DD739D3321F20C4109B56467C86C16 — Uploads/dxsharp/SharpDX.DXGI.dll
SHA256: 4E50D554D7D90A82C440E414521A217CC89600D5629CA8177AE8E76A241FF524 — Uploads/libs/RakNet.dll
SHA256: 8BB1B93D1073C384BBAC88E77A87B27F899BCC7D5973ACC12ECF93343AD15305 — Uploads/libs/Rust.Data.dll
SHA256: 920FBD6718B4DBA5D36971ABC93D5A0B777437A967C8360E1141B70226197431 — Uploads/libs/UnityEngine.dll

Download:

Last edited by dorfmidge; 22nd November 2017 at 06:29 AM.
Reason: some credits i forgot

dorfmidge is offline

Old
4th October 2017, 11:37 AM

hitmangmod

Junior Member

Join Date: Nov 2016

Posts: 39

Reputation: -392

Rep Power: 0

Points: 981, Level: 2

Level up: 17%, 419 Points needed

Activity: 1.2%

thx man very helpful

where was that switch case?

hitmangmod is offline

Old
4th October 2017, 05:48 PM

F3t

Junior Member

Join Date: Sep 2017

Posts: 52

Reputation: 937

Rep Power: 133

Recognitions

Donator

(2)

Points: 1,972, Level: 3

Level up: 82%, 128 Points needed

Activity: 3.3%

Last Achievements

Extremely helpful, I had made my own overlay using the interceptor but as I said in my first post I’m just learning.

I think you’re missing:
public bool IsPlant { get { return proto.plantEntity != null; } }

In Entity.cs. Am I wrong on that?

F3t is offline

Old
4th October 2017, 07:37 PM

hitmangmod

Junior Member

Join Date: Nov 2016

Posts: 39

Reputation: -392

Rep Power: 0

Points: 981, Level: 2

Level up: 17%, 419 Points needed

Activity: 1.2%

Quote:

Originally Posted by F3t

Extremely helpful, I had made my own overlay using the interceptor but as I said in my first post I’m just learning.

I think you’re missing:
public bool IsPlant { get { return proto.plantEntity != null; } }

In Entity.cs. Am I wrong on that?

can u help me a bit in steam?

hitmangmod is offline

Old
4th October 2017, 07:47 PM

Naex

Senior Member

Join Date: Apr 2017

Location: Snow nigger

Posts: 87

Reputation: -96

Rep Power: 0

Points: 1,059, Level: 2

Level up: 32%, 341 Points needed

Activity: 0%

Damn this guy is a legend
Thanks a lot for this information.
Releasing this to the public might make it client-sided detected right?
So would changing the code a bit change that?

Naex is offline

Old
4th October 2017, 11:43 PM

F3t

Junior Member

Join Date: Sep 2017

Posts: 52

Reputation: 937

Rep Power: 133

Recognitions

Donator

(2)

Points: 1,972, Level: 3

Level up: 82%, 128 Points needed

Activity: 3.3%

Last Achievements

So I faithfully tried to follow the instructions but I got stuck after compiling the Interceptor. Would it be possible to PM me the source?

The instructions for Motor.cs don’t instantiate the Interceptor, and after that everything becomes very confusing.

F3t is offline

Old
5th October 2017, 12:09 AM

dadasda

n00bie

Join Date: May 2017

Posts: 4

Reputation: 10

Rep Power: 142

Can you help please I get an error saying :
The name ‘GetName’ does not exist in the current context

dadasda is offline

Old
5th October 2017, 04:39 AM

dorfmidge

Red Fish, Blue Fish, «blowfish», «twofish»

Threadstarter

Join Date: Aug 2014

Location: namespace

Posts: 60

Reputation: 2624

Rep Power: 210

Recognitions

Donator

(9)

Points: 9,004, Level: 11

Level up: 28%, 796 Points needed

Activity: 1.7%

Last Achievements

I’ll do some fixes when I get home. But there is some places In here to stop you from directly copy pasting that will make it break or crash. I want you to actually learn from it and figure out how to make it completed and work .

dorfmidge is offline

Old
5th October 2017, 06:29 AM

hitmangmod

Junior Member

Join Date: Nov 2016

Posts: 39

Reputation: -392

Rep Power: 0

Points: 981, Level: 2

Level up: 17%, 419 Points needed

Activity: 1.2%

a bit help

hitmangmod is offline

Old
5th October 2017, 10:22 AM

#10

jdilly69

h4x0!2

Join Date: Sep 2015

Posts: 91

Reputation: 36

Rep Power: 0

Thanks , This helped alot.

jdilly69 is offline

Old
5th October 2017, 03:16 PM

#11

hotice121

n00bie

Join Date: Oct 2017

Posts: 15

Reputation: 10

Rep Power: 132

Thanks again this helped me get started.

hotice121 is offline

Old
5th October 2017, 03:18 PM

#12

F3t

Junior Member

Join Date: Sep 2017

Posts: 52

Reputation: 937

Rep Power: 133

Recognitions

Donator

(2)

Points: 1,972, Level: 3

Level up: 82%, 128 Points needed

Activity: 3.3%

Last Achievements

Quote:

Originally Posted by dorfmidge

I found and fixed the things in the Interceptor that were copy/paste protection.

But past that it gets dicey, heh.

Oh, to help people. GetName doesn’t exist on purpose, you have to figure out the logic and write it yourself. The logic on «Envrecouse» is that it’s a collectable environmental resource, like wood/stone/etc. I think unfortunately it also lists mushrooms etc too, which I personally do not want on the ESP.

So all you need to do is fix the spelling (resource, was driving me nuts :P) and use StringPool to convert the prefab id, a uint, to a String, so that the logic works.

Code:

        public bool IsEnvresource
        {
            get
            {
                if ((GetName(Data.baseNetworkable.prefabID)) == null) return false;
                return proto.baseEntity != null && (GetName(Data.baseNetworkable.prefabID)).ToLower().Contains("collectable");
            }
        }

I also rewrote the function to make it more readable.

F3t is offline

Old
5th October 2017, 10:22 PM

#13

MarkHC

Hacked North Korea

Join Date: May 2012

Location: Brazil

Posts: 2,688

Reputation: 68729

Rep Power: 358

Recognitions

Former Staff

Donator

(1)

Points: 97,425, Level: 45

Level up: 38%, 3,575 Points needed

Activity: 1.5%

Last Achievements

File Approved

SHA256: A3A5FE262EA5E985DC7EEE4298F4B4293779C34B8CD2E471A701F95B0710CC63 — Uploads/dxsharp/SharpDX.Direct2D1.dll
SHA256: 97CC9005F58BBBF898EABBADFAF45A994190F7088AD353648CB719D9F9313CBB — Uploads/dxsharp/SharpDX.dll
SHA256: 1F574BE760ECA0A59D43DF68BE0BF0C119DD739D3321F20C4109B56467C86C16 — Uploads/dxsharp/SharpDX.DXGI.dll
SHA256: 4E50D554D7D90A82C440E414521A217CC89600D5629CA8177AE8E76A241FF524 — Uploads/libs/RakNet.dll
SHA256: 8BB1B93D1073C384BBAC88E77A87B27F899BCC7D5973ACC12ECF93343AD15305 — Uploads/libs/Rust.Data.dll
SHA256: 920FBD6718B4DBA5D36971ABC93D5A0B777437A967C8360E1141B70226197431 — Uploads/libs/UnityEngine.dll

Interested in how we analyze files? Click here to find out.

__________________

[email protected]:~$
rule 7.

MarkHC is online now

Old
6th October 2017, 05:34 AM

#14

dorfmidge

Red Fish, Blue Fish, «blowfish», «twofish»

Threadstarter

Join Date: Aug 2014

Location: namespace

Posts: 60

Reputation: 2624

Rep Power: 210

Recognitions

Donator

(9)

Points: 9,004, Level: 11

Level up: 28%, 796 Points needed

Activity: 1.7%

Last Achievements

Quote:

Originally Posted by F3t

I found and fixed the things in the Interceptor that were copy/paste protection.

But past that it gets dicey, heh.

So all you need to do is fix the spelling (resource, was driving me nuts :P) and use StringPool to convert the prefab id, a uint, to a String, so that the logic works.

Code:

        public bool IsEnvresource
        {
            get
            {
                if ((GetName(Data.baseNetworkable.prefabID)) == null) return false;
                return proto.baseEntity != null && (GetName(Data.baseNetworkable.prefabID)).ToLower().Contains("collectable");
            }
        }

I also rewrote the function to make it more readable.

I was kinda wondering if someone would notice the spelling lol. HINT there is another bool add to get stone metal and sulfur nodes

You have to add it to entity.cs in the interceptor

I should I make a wrapper for rust interceptor and an overlay ?

Last edited by dorfmidge; 6th October 2017 at 05:41 AM.

dorfmidge is offline

Old
6th October 2017, 08:48 AM

#15

emir223

1337 H4x0!2

Join Date: Dec 2015

Posts: 130

Reputation: -262

Rep Power: 0

Points: 2,259, Level: 4

Level up: 23%, 541 Points needed

Activity: 2.0%

Last Achievements

u are god bro thank u!

emir223 is offline

Old
8th October 2017, 05:48 PM

#16

hitmangmod

Junior Member

Join Date: Nov 2016

Posts: 39

Reputation: -392

Rep Power: 0

Points: 981, Level: 2

Level up: 17%, 419 Points needed

Activity: 1.2%

dude stop fucking me in the ass if its really hard to ask my question cuz my eng is bad just say I will no more ask for help thx

hitmangmod is offline

Old
9th October 2017, 06:45 AM

#17

dorfmidge

Red Fish, Blue Fish, «blowfish», «twofish»

Threadstarter

Join Date: Aug 2014

Location: namespace

Posts: 60

Reputation: 2624

Rep Power: 210

Recognitions

Donator

(9)

Points: 9,004, Level: 11

Level up: 28%, 796 Points needed

Activity: 1.7%

Last Achievements

Cmon dude I’m not going to give you a 1:1 copy go to the «other» forum for that shit. You should be about to figure this out. Honestly most people here figured out out on their own useing the pci-e slot on their cerebral cord

dorfmidge is offline

Old
9th October 2017, 10:46 AM

#18

hitmangmod

Junior Member

Join Date: Nov 2016

Posts: 39

Reputation: -392

Rep Power: 0

Points: 981, Level: 2

Level up: 17%, 419 Points needed

Activity: 1.2%

yeah youre right I should stop bitching around for a help thx anyway

__________________

shitty eng and learning C fucking #

hitmangmod is offline

Old
10th October 2017, 10:54 PM

#19

njbrown09

n00bie

Join Date: Jun 2017

Posts: 18

Reputation: 10

Rep Power: 139

How are you doing packet forging? Im trying to do the remove the wall thing but i get entities out of order. Is there a way to serialize Protobuf entity?

njbrown09 is offline

Old
11th October 2017, 08:17 AM

#20

dorfmidge

Red Fish, Blue Fish, «blowfish», «twofish»

Threadstarter

Join Date: Aug 2014

Location: namespace

Posts: 60

Reputation: 2624

Rep Power: 210

Recognitions

Donator

(9)

Points: 9,004, Level: 11

Level up: 28%, 796 Points needed

Activity: 1.7%

Last Achievements

Quote:

Originally Posted by njbrown09

How are you doing packet forging? Im trying to do the remove the wall thing but i get entities out of order. Is there a way to serialize Protobuf entity?

Hint: the first byte of the packet is the type 0 — 255 see how entity gets the type for more info the next 4 bytes (uint) is the entity order. you will have to change the entity order on the packet and the rest of the packets if you make a new packet

modified packet: change only on the mod packet
Forged (new) packet: change on all the other packets and the rest

Last edited by dorfmidge; 11th October 2017 at 10:13 AM.

dorfmidge is offline

Page 1 of 4

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Question] Is there a way to make proxy dlls in win10?	wwwc	General Programming and Reversing	6	10th April 2017 09:59 PM
[Help] I can make things like a basic ESP/Aimbot and hack, what now?	FE3KA	C and C++	13	8th October 2014 02:03 PM
[Source] basic player and wall evasion (auto_direction + basic auto_br)	david_BS	CounterStrike 1.5, 1.6 and Mods	0	30th January 2012 03:08 PM
[Information] Bones! (Enough to make a basic bone esp)	Big Dave	Battlefield Play4Free	14	26th April 2011 09:41 PM
[Tutorial] Visual Basic Trainer Example (How to write a visual basic trainer)	Snake	VB.NET	15	19th May 2007 12:37 AM

Rust on ESP-IDF «Hello, World» template

A «Hello, world!» template, to use with cargo-generate, of a Rust binary crate for the ESP-IDF framework.

This is the crate you get when running cargo new, but augmented with extra configuration so that it does build for the ESP32[XX] with ESP-IDF and (by default) with STD support.

Or if you rather

… want to mix Rust and C/C++ in a traditional ESP-IDF idf.py CMake project — follow these instructions
… want to mix Rust and C/C++ with PlatformIO — follow these instructions

Generate the project

Please make sure you have installed all prerequisites first!

cargo generate https://github.com/esp-rs/esp-idf-template cargo

The command will display a few prompts:

Project Name: Name of the crate.
Which MCU to target?: SoC model, e.g. esp32, esp32s2, esp32c3 etc.
STD support: When true (default), adds support for the Rust Standard Library. Otherwise, a no_std Rust Core Library crate would be created.
ESP-IDF Version: ESP-IDF branch/tag to use. Possible choices:
- v.4.4: Stable
- v.4.3.2: Previous stable
- mainline: Unstable
Dev Containers support?: Adds support for:
- VS Code Dev Containers
- GitHub Codespaces
- Gitpod
  Dev Containers also have integration with Wokwi simulator and allow flashing from the container using web flash.

Build

cd <your-project-name>
cargo build

Replace <your-project-name> with the name of the generated project

Flash

In the root of the generated project:

espflash /dev/ttyUSB0 target/[xtensa-esp32-espidf|xtensa-esp32s2-espidf|xtensa-esp32s3-espidf|riscv32imc-esp-espidf]/debug/<your-project-name>

Replace dev/ttyUSB0 above with the USB port where you’ve connected the board. If you do not
specify any USB port, espflash will print a list of the recognized USB ports for you to select
the desired port.
Replace <your-project-name> with the name of the generated project
You can include the --monitor argument to the espflash command to open a serial monitor after flashing the device.
For more details on espflash usage see the README

Monitor

espflash monitor /dev/ttyUSB0

Replace dev/ttyUSB0 above with the USB port where you’ve connected the board. If you do not
specify any USB port, cargo-espflash/espflash will print a list of the recognized USB ports for you to select
the desired port.

The monitor should output more or less the following:

Opening /dev/tty.usbserial-0001 with speed 115200
Resetting device... done
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0048,len:12
ho 0 tail 12 room 4
load:0x3fff0054,len:4800
load:0x40078000,len:17448
load:0x4007c428,len:4840
entry 0x4007c6a0
I (178) cpu_start: Pro cpu up.
I (178) cpu_start: Starting app cpu, entry point is 0x4008115c
I (0) cpu_start: App cpu up.
I (193) cpu_start: Pro cpu start user code
I (193) cpu_start: cpu freq: 160000000
I (193) cpu_start: Application information:
I (197) cpu_start: Project name:     esp-idf
I (202) cpu_start: App version:      f08dcd7
I (207) cpu_start: Compile time:     Oct 23 2021 14:48:03
I (213) cpu_start: ELF file SHA256:  0000000000000000...
I (219) cpu_start: ESP-IDF:          4.3.0
I (224) heap_init: Initializing. RAM available for dynamic allocation:
I (231) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (237) heap_init: At 3FFB3498 len 0002CB68 (178 KiB): DRAM
I (243) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (250) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (256) heap_init: At 4008C538 len 00013AC8 (78 KiB): IRAM
I (263) spi_flash: detected chip: generic
I (267) spi_flash: flash io: dio
I (272) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
Hello, world!

Prerequisites

Install Rust (with `rustup`)

If you don’t have rustup installed yet, follow the instructions on the rustup.rs site

Install Cargo Sub-Commands

cargo install cargo-generate
cargo install ldproxy
cargo install espup
cargo install espflash
cargo install cargo-espflash # Optional

Note

If you are running macOS or Linux then libuv must also be installed for espflash and cargo-espflash; this is available via most popular package managers. If you are running Windows you can ignore this step.
# macOS
brew install libuv
# Debian/Ubuntu/etc.
apt-get install libuv-dev
# Fedora
dnf install systemd-devel
Also, the espflash and cargo-espflash commands shown below, assume that version 2.0 or
greater.

Install Rust & Clang toolchains for Espressif SoCs (with `espup`)

espup install
# Unix
. $HOME/export-esp.sh
# Windows
%USERPROFILE%export-esp.ps1

Warning

Make sure you source the generated export file, as shown above, in every terminal before building any application as it contains the required environment variables.

See the Installation chapter of The Rust on ESP Book for more details.

Alternative (for RISC-V Espressif SOCs only): install & use upstream Rust & Clang

While you can target the RISC-V Espressif SOCs (esp32-cXX and esp32-hXX) with the espup installer just fine, SOCs with this architecture are also supported by the nightly Rust compiler and by recent, stock Clang compilers (as in Clang 11+):

Install a recent Clang. See Clang Getting Started page as it contains useful guidelines on instalaltion. Recent Linux distros come with suitable Clang already.
Install the nightly Rust toolchain with the rust-src component included:
```
rustup toolchain install nightly --component rust-src
```

(Windows-only) Install Python3

You need a Python 3.7 or later installed on your machine. Install it from the official Python site.

Источник

I have been working with ESPs, for playing around in the space of IoT, for a while now. Mostly using the ESP8266 and Espressif, through platform.io. In recent times, I have also started to really like Rust as programming language. And I really believe that all Rust has to offer, would be great match for embedded development. So when I had a bit of time, I wanted to give it a try. And here is what came out of it …

Up until now I only used the ESP and Rust on a very high level. So I was hoping to get some kind of an “out-of-the-box” solution. Well, we are not there yet. But my only intention was to play around a bit with the technology. And so I started to search what others had done in this area already.

LLVM & Rust

Rust, or more precisely, the default rust compiler is based on LLVM. It compiles rust code by parsing it and handing it over to the LLVM toolchain at some point. So as soon as LLVM can create code for the Xtensa target (the CPU of the ESP), that first step of being able to compile code for the ESP should be achieved.

The good news: work for this is already underway. There is a fork of LLVM for Xtensa, which seems to be provided by the people behind the Espressif framework. Having support for LLVM will enable all other kinds of integrations, Rust for the ESP is just one of them. The bad news: this is more or less “compile your own”. And have you ever compiled a compiler, which is needed to compile a compiler?

So the next step, after compiling LLVM (on a x64 target, with the ability to cross compile to Xtensa) is to compile Rust itself. Actually, that wasn’t too bad. It takes a while, but the process of compiling Rust with a provided version of LLVM is more or less straight forward. Assuming that you use a version of Rust, patched for providing the Xtensa target architectures, which is already available on GitHub at MabezDev/rust-xtensa (be sure to use the xtensa-target branch).

Cross compiling with Rust

After this, you are basically set up for getting started. However, it still is a bit complicated, as you do need to cross compile with Rust for the ESP. You are running Rust on your host machine (x64) and want to build for the Xtensa target architecture. This requires also to compile the core Rust crate for that architecture. This is where xargocomes into play.

Xargo helps you build your project (like cargo), but it also supports building the “sysroot”, which is required by each rust application. I know that on the Xargo GitHub repository you will find a note, which says that it is in “maintenance mode”. But for one, the tool just works and does what it should do. And second, I also do understand the original author of the tool, setting the right expectations. It also seems that there is work underway in Rust to make this tool obsolete. Maybe it already is done and I just need to check

ESP Hardware Abstraction Layer

So we have a compiler now, and the core foundation to run Rust on the Xtensa architecture. But of course, we do want to interact with the ESP functionalities. At least, let an LED blink or print something out on the serial console.

And this is where it gets complicated. When running on an embedded system, you don’t have a “kernel”, you don’t have “drivers” and you don’t have something like a “libc”, which does all the work for you, and that e.g. Rust can be based upon. The right thing to do would be to start writing everything in Rust, from scratch. Having a full “std” crate on Rust, would basically allow you to re-use all the “rust native” crates that are available on crates.io. At least as long as they fit into your embedded system of course

But we don’t (yet) have a “standard crate”, we only have the bare minimum “core” crate to work with. Now, there is a simple way around this. And yes, it feels a little bit like cheating.

The Espressif IoT Development Framework framework (IDF) already provides all kinds of drivers and components to work with the hardware of the ESP. So, why not re-use that? A good reason to not re-use that is, that it is not written in Rust, and has all the problems of classic C code. But on the other side, it is available right now

Wiring up ESP-IDF

In a nutshell, the IDF is a framework, which provides all the required bits and pieces to create applications on top of the ESP. It is written in C, and provides you with a modular build system (welcome back make menuconfig) that allows you to select which components and features you would like to compile in.

The basic idea is to build a normal “ESP-IDF” based project. And then you use Rust to build your application, pulling in everything except the C based “main” method from that project. That way, when your application starts up, you have the ESP HAL from the IDF, but your Rust application code.

The final step is to allow your Rust code to call into the C code of the ESP-IDF. You can use a tool called bindgen from Rust, in order to achieve this. Bindgen creates Rust bindings for C libraries, and this is exactly what we are looking for.

There is a basic example at lexxvir/esp32-hello, but it took me a while to tweak it and get it working. It also only uses the UART, which also pulls in the GPIO, but it shows the basic concept of the idea.

Making Rust for ESP “out-of-the-box”

Figuring out all of this, and getting it actually working, took me the better part of a Saturday. It was fun digging a little bit into all of this, but it would be great if there was this “out-of-the-box” solution that I was looking for. Honestly I forgot probably half of the pitfalls when writing up this blog post. And didn’t tell you about the hours and hours of compiling and re-compiling.

So I did write it all up in a Dockerfile (full repository: ctron/rust-esp-container). And crated an automated build for that on quay.io. Why not Docker Hub? Because it couldn’t handle the build. The builds ran much longer, and always timed out before they were even close to complete. And this container isn’t a small one. Even after cleaning up intermediate layers, it still is around 5GiB.

Now it is possible to just use docker, mapping a local folder into that container, and let the pre-compiled Xtensa toolchain do the build. There is a short introduction in the README, which should help you get started pretty quickly.

Caveats & What’s next?

Getting started with Rust on the ESP, based on the ESP-IDF HAL is much easier now. However, most of your code will therefore still be C based. Of course that may be OK for you, but using the IDF specific APIs also prevents you from using Rust crates, which expect the Rust standard library. Network access and thus HTTP calls (which was my goal in the beginning) is just one of this. So instead of just using reqwest, you will need to map in the HTTP layer from IDF, bindgen this to rust in order to do HTTP.

So my hope is that there all the temporary changes and forks, used in this setup, get merged into their upstream sources. LLVM and Rust directly supporting Xtensa. So, that the next step, can be to build some standard library support for Rust. And so you would be able to use most of Rust’s ecosystem on an ESP, without too much trouble.

But for me, I am happy to share my experience, and try to provide this container image in order to make things easier for people that want to get started quickly. I will be trying to improve this, after all, my goal of sending HTTP requests from Rust it not yet reached. After all, this helps me to not re-start from scratch, every time I find a few minutes to play around with this. And maybe it helps you as well.

If you find any bugs or have improvements, contributions are always welcome.

Thanks to …

I would have never been able to figure all of this out, without the help of:

https://quickhack.net/nom/blog/2019-05-14-build-rust-environment-for-esp32.html
https://esp32.com/viewtopic.php?t=9226
https://github.com/MabezDev/rust-xtensa
https://github.com/lexxvir/esp32-hello

Jens Reimann

Working on Eclipse IoT projects for a living. Enjoying a good technical challenge.

This is my personal blog.

118 posts

Источник

Since my last post, nearly 10 months ago a lot has changed. For one, its not just me working on this any more! Community members are starting to contribute to the various ESP related projects. The extra help meant we have made considerable progress which I will now take you through in this post.

The compiler

I have been working on cleaning up the rustc work, including rebasing regularly to keep up with upstream rustc changes. Recently, I have cleaned up and extracted the patches required to enable Xtensa & esp development with Rust, firstly to make it easier to rebase onto a newer version of the compiler, but also in the hopes of one day being able to submit these patches upstream when the Xtensa target is upstreamed in llvm. You can see the patchset here. On that note, it seems no progress has been made on that front in the last 9 months; whilst Espressif are doing a great job responding to issues and fixing bugs, it seems the patches are stuck in review in llvm. I’m unsure what directions to take to get more attention to this.

I have also reworked the build process, as well as tagging releases. It is no longer necessary to build LLVM seperately, as I have swapped out the LLVM submodule to the forked one, meaning you can just use normal rust build instructions. Starting now, I will also be tagging releases every time I rebase on upstream master; on top of which I am also offering prebuilt linux (sorry Windows & Mac users) toolchains on the releases (if you are building for Mac or Windows, please feel free to send me your prebuilt toolchains for upload).

cargo-espflash

For those of you not familiar with developing on ESP* platforms, there is a flashing tool esptool.py which will flash your program to the device. @icewind1991 began rewriting this tool in Rust, called espflash. @jessebraham then submitted a PR which added a cargo interface to it, meaning we can easily build and flash all in one go, for example building and flashing the blinky example in the ESP32 HAL:

$ cargo espflash --chip esp32 --example blinky /dev/ttyUSB0

It’s really nice to invoke cargo once, make a coffee, and have your code running on the board when you get back! We’ve been adding more features to the tool, like reading back board info (flash size, CPU revision etc) in #3, and allowing faster flash speeds for the ESP32 in #5.

idf2svd

@jessebraham submitted a PR to idf2svd to add support for generating ESP8266 SVD’s, of which the esp8266-hal is built upon; if you remeber back to the bonus section of my last post, you will be able to use that SVD to debug ESP8266 applications too!

The runtime crates

After my last post I set to improve the runtime crate to include support for exceptions, which I started before taking a short break. In that time @arjanmels championed it, fully implementing exception and interrupt handling for the lx6 CPU of the ESP32! On top of that, for those of you familiar with the cortex-m-rt crates, we implemented the attribute macros for defining #[interrupt]/#[exception] handlers and the #[entry] point to the program. Previously xtensa-lx6 was empty, but we have since implemented (and moved code from rt where neccessary), including the on chip timers and a series of mutex implementations for the platform.

Meanwhile @icewind1991 began writing a runtime crate for the lx106, the processor in a ESP8266. We found that between the xtensa-lx series there were not many differences, confirming what a core esp-idf developer mentioned previously, therefore we decided to merge the lx6 and lx106 crates producing xtensa-lx and xtensa-lx-rt with features for each silicon revision.

The HAL crates

ESP32

With the runtime crates in good shape, we now had a good basis to build a HAL (Hardware abstraction layer). I started by submitting a simple GPIO driver for the ESP32 implementing the embedded-hal digital traits. Since then the features haven’t stopped coming, primarily thanks once again to @arjanmels. Checkout the examples to see what you can do with an ESP32 in pure Rust¹!

ESP8266

@icewind1991 has since started the ESP8266 HAL. One thing that is slowing down development is the fact that alot of the functions in the C SDK are simply binary blobs (or as Espressif refer to them, ROM functions). It means that re-implementing them in Rust requires disassembly of the binaries and reverse engineering of the assembly to figure out whats going on. Whilst it is undoubtedly fun, it is a lot harder than looking at the source (which we can do with the ESP32). It’s coming along nicely though, with support for GPIO, Serial, SPI and much more. Checkout the esp-rs/esp8266-hal repo. @jessebraham has started a BSP (board support package) for the D1 Mini ESP8266 board, built on top of the esp8266-hal, so if you have one of those board lying around check out the repo!

The quickstart

With the compiler changes and HAL’s being created, the old quickstart needed some love. First on the list removing some unneeded compiler restrictions, mainly around allowing debug info generation, as the LLVM fork now supports that (See #23). The biggest change has been adding runnable examples for both the ESP32 & ESP8266; its now easier than ever to Rustup your Esp microcontroller! I have also added a brief overview of how to target a different Xtensa target other than the ESP32 or ESP8266, though I’m not aware of any other boards using this architecture, would be very interested to hear about it if you are aware of any.

What’s next?

I’d love to see more contributors as it’s easier than ever to contribute if you are familiar with Rust or embedded; both HAL’s are in a good spot to pick a hardware feature and implement it in Rust!
Myself and @arjanmels are looking at WiFi/Bluetooth support for the ESP32, but haven’t had much luck so far.
At some point I’d like to start looking into integrating with an existing Rust RTOS, perhaps tockos or rtic.

At this point I’d like to say a big thank you to all the contributors who have helped along the way so far!

Finally, if you appreciate the effort going into this, consider joining @davidkern, @DaMouse404 and others in sponsoring me, it’s very much appreciated <3.

Источник

The Rust on ESP Book

Introduction

The goal of this book is to provide a comprehensive guide on using the Rust programming language with Espressif SoCs and modules.

Rust support for these devices is still a work in progress, and progress is being made rapidly. Because of this, parts of this documentation may be out of date or change dramatically between readings.

For tools and libraries relating to Rust on ESP, please see the esp-rs organization on GitHub.

A note in SoCs support

The content of the books applies to ESP32, ESP32-S, and ESP32-C series of SoCs.
ESP8266 series is out of the scope of this book, support for Rust in ESP8266 is limited and only some parts
of the book are applicable for this SoC.

Status of This Book

This book is currently a work in progress. A number of sections may be missing information or be missing altogether. If there is a specific topic you would like to see documented please open an issue.

If you feel you can contribute something to this book, we encourage you to create a pull request!

Who This Book is For

This book assumes some experience with embedded development and the Rust programming language. Teaching these topics is outside the scope of this book.

If you are unfamiliar with either topic, please refer to the resources listed below to help you get started.

Additional Resources

Some additional resources can be found below which may prove useful for those less experienced with embedded Rust.

Источник

I’m using this example as boilerplate for a PoC I’m conducting. I’m compiling with the docker image georgikrocks/esp-idf-rust:latest (2e95100a412d). When my Rust code calls rand::thread_rng(), compilation fails with

FAILED: streams-embedded-transport-example.elf 
: && /opt/xtensa-esp32-elf-clang/bin/xtensa-esp32-elf-g++ -mlongcalls -Wno-frame-address  CMakeFiles/streams-embedded-transport-example.elf.dir/project_elf_src_esp32.c.obj -o streams-embedded-transport-example.elf  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/asio/libasio.a  esp-idf/cbor/libcbor.a  esp-idf/unity/libunity.a  esp-idf/cmock/libcmock.a  esp-idf/coap/libcoap.a  esp-idf/console/libconsole.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/esp_adc_cal/libesp_adc_cal.a  esp-idf/esp_hid/libesp_hid.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/esp_lcd/libesp_lcd.a  esp-idf/protobuf-c/libprotobuf-c.a  esp-idf/protocomm/libprotocomm.a  esp-idf/mdns/libmdns.a  esp-idf/esp_local_ctrl/libesp_local_ctrl.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/esp_websocket_client/libesp_websocket_client.a  esp-idf/expat/libexpat.a  esp-idf/wear_levelling/libwear_levelling.a  esp-idf/fatfs/libfatfs.a  esp-idf/freemodbus/libfreemodbus.a  esp-idf/jsmn/libjsmn.a  esp-idf/json/libjson.a  esp-idf/libsodium/liblibsodium.a  esp-idf/mqtt/libmqtt.a  esp-idf/openssl/libopenssl.a  esp-idf/perfmon/libperfmon.a  esp-idf/spiffs/libspiffs.a  esp-idf/ulp/libulp.a  esp-idf/wifi_provisioning/libwifi_provisioning.a  esp-idf/main/libmain.a  esp-idf/clib/libclib.a  esp-idf/rustlib/librustlib.a  -Wl,--cref -Wl,--Map=/opt/streams/build/streams-embedded-transport-example.map  -Wl,--gc-sections  -fno-rtti  -fno-lto  esp-idf/asio/libasio.a  esp-idf/cbor/libcbor.a  esp-idf/cmock/libcmock.a  esp-idf/unity/libunity.a  esp-idf/coap/libcoap.a  esp-idf/esp_adc_cal/libesp_adc_cal.a  esp-idf/esp_hid/libesp_hid.a  esp-idf/esp_lcd/libesp_lcd.a  esp-idf/esp_local_ctrl/libesp_local_ctrl.a  esp-idf/esp_websocket_client/libesp_websocket_client.a  esp-idf/expat/libexpat.a  esp-idf/fatfs/libfatfs.a  esp-idf/wear_levelling/libwear_levelling.a  esp-idf/freemodbus/libfreemodbus.a  esp-idf/jsmn/libjsmn.a  esp-idf/libsodium/liblibsodium.a  esp-idf/mqtt/libmqtt.a  esp-idf/openssl/libopenssl.a  esp-idf/perfmon/libperfmon.a  esp-idf/spiffs/libspiffs.a  esp-idf/wifi_provisioning/libwifi_provisioning.a  esp-idf/protocomm/libprotocomm.a  esp-idf/protobuf-c/libprotobuf-c.a  esp-idf/mdns/libmdns.a  esp-idf/console/libconsole.a  esp-idf/json/libjson.a  esp-idf/rustlib/target/xtensa-esp32-espidf/release/librustlib.a  esp-idf/clib/libclib.a  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/ulp/libulp.a  esp-idf/mbedtls/mbedtls/library/libmbedtls.a  esp-idf/mbedtls/mbedtls/library/libmbedcrypto.a  esp-idf/mbedtls/mbedtls/library/libmbedx509.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcoexist.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcore.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libespnow.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libmesh.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libnet80211.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libpp.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libsmartconfig.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libwapi.a  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/ulp/libulp.a  esp-idf/mbedtls/mbedtls/library/libmbedtls.a  esp-idf/mbedtls/mbedtls/library/libmbedcrypto.a  esp-idf/mbedtls/mbedtls/library/libmbedx509.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcoexist.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcore.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libespnow.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libmesh.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libnet80211.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libpp.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libsmartconfig.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libwapi.a  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/ulp/libulp.a  esp-idf/mbedtls/mbedtls/library/libmbedtls.a  esp-idf/mbedtls/mbedtls/library/libmbedcrypto.a  esp-idf/mbedtls/mbedtls/library/libmbedx509.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcoexist.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcore.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libespnow.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libmesh.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libnet80211.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libpp.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libsmartconfig.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libwapi.a  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/ulp/libulp.a  esp-idf/mbedtls/mbedtls/library/libmbedtls.a  esp-idf/mbedtls/mbedtls/library/libmbedcrypto.a  esp-idf/mbedtls/mbedtls/library/libmbedx509.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcoexist.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcore.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libespnow.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libmesh.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libnet80211.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libpp.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libsmartconfig.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libwapi.a  esp-idf/esp_ringbuf/libesp_ringbuf.a  esp-idf/efuse/libefuse.a  esp-idf/esp_ipc/libesp_ipc.a  esp-idf/driver/libdriver.a  esp-idf/esp_pm/libesp_pm.a  esp-idf/mbedtls/libmbedtls.a  esp-idf/app_update/libapp_update.a  esp-idf/bootloader_support/libbootloader_support.a  esp-idf/spi_flash/libspi_flash.a  esp-idf/nvs_flash/libnvs_flash.a  esp-idf/pthread/libpthread.a  esp-idf/esp_gdbstub/libesp_gdbstub.a  esp-idf/espcoredump/libespcoredump.a  esp-idf/esp_phy/libesp_phy.a  esp-idf/esp_system/libesp_system.a  esp-idf/esp_rom/libesp_rom.a  esp-idf/hal/libhal.a  esp-idf/vfs/libvfs.a  esp-idf/esp_eth/libesp_eth.a  esp-idf/tcpip_adapter/libtcpip_adapter.a  esp-idf/esp_netif/libesp_netif.a  esp-idf/esp_event/libesp_event.a  esp-idf/wpa_supplicant/libwpa_supplicant.a  esp-idf/esp_wifi/libesp_wifi.a  esp-idf/lwip/liblwip.a  esp-idf/log/liblog.a  esp-idf/heap/libheap.a  esp-idf/soc/libsoc.a  esp-idf/esp_hw_support/libesp_hw_support.a  esp-idf/xtensa/libxtensa.a  esp-idf/esp_common/libesp_common.a  esp-idf/esp_timer/libesp_timer.a  esp-idf/freertos/libfreertos.a  esp-idf/newlib/libnewlib.a  esp-idf/cxx/libcxx.a  esp-idf/app_trace/libapp_trace.a  esp-idf/nghttp/libnghttp.a  esp-idf/esp-tls/libesp-tls.a  esp-idf/tcp_transport/libtcp_transport.a  esp-idf/esp_http_client/libesp_http_client.a  esp-idf/esp_http_server/libesp_http_server.a  esp-idf/esp_https_ota/libesp_https_ota.a  esp-idf/sdmmc/libsdmmc.a  esp-idf/esp_serial_slave_link/libesp_serial_slave_link.a  esp-idf/ulp/libulp.a  esp-idf/mbedtls/mbedtls/library/libmbedtls.a  esp-idf/mbedtls/mbedtls/library/libmbedcrypto.a  esp-idf/mbedtls/mbedtls/library/libmbedx509.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcoexist.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libcore.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libespnow.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libmesh.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libnet80211.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libpp.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libsmartconfig.a  /opt/esp/idf/components/esp_wifi/lib/esp32/libwapi.a  -Wl,--wrap=mbedtls_mpi_exp_mod  -u esp_app_desc  -u pthread_include_pthread_impl  -u pthread_include_pthread_cond_impl  -u pthread_include_pthread_local_storage_impl  -L /opt/esp/idf/components/esp_phy/lib/esp32  -lphy  esp-idf/esp_phy/libesp_phy.a  -lphy  esp-idf/esp_phy/libesp_phy.a  -lphy  -lrtc  -u ld_include_highint_hdl  -u start_app  -u start_app_other_cores  -L /opt/streams/build/esp-idf/esp_system/ld  -T memory.ld  -T sections.ld  -u __ubsan_include  -L /opt/esp/idf/components/esp_rom/esp32/ld  -T esp32.rom.ld  -T esp32.rom.api.ld  -T esp32.rom.libgcc.ld  -T esp32.rom.newlib-data.ld  -T esp32.rom.syscalls.ld  -T esp32.rom.newlib-funcs.ld  -T esp32.rom.newlib-time.ld  -Wl,--wrap=longjmp  -u __assert_func  -u vfs_include_syscalls_impl  -L /opt/esp/idf/components/esp_wifi/lib/esp32  -L /opt/esp/idf/components/soc/esp32/ld  -T esp32.peripherals.ld  /opt/esp/idf/components/xtensa/esp32/libxt_hal.a  -Wl,--undefined=uxTopUsedPriority  -u app_main  -lm  esp-idf/newlib/libnewlib.a  -u newlib_include_heap_impl  -u newlib_include_syscalls_impl  -u newlib_include_pthread_impl  -Wl,--wrap=_Unwind_SetEnableExceptionFdeSorting  -Wl,--wrap=__register_frame_info_bases  -Wl,--wrap=__register_frame_info  -Wl,--wrap=__register_frame  -Wl,--wrap=__register_frame_info_table_bases  -Wl,--wrap=__register_frame_info_table  -Wl,--wrap=__register_frame_table  -Wl,--wrap=__deregister_frame_info_bases  -Wl,--wrap=__deregister_frame_info  -Wl,--wrap=_Unwind_Find_FDE  -Wl,--wrap=_Unwind_GetGR  -Wl,--wrap=_Unwind_GetCFA  -Wl,--wrap=_Unwind_GetIP  -Wl,--wrap=_Unwind_GetIPInfo  -Wl,--wrap=_Unwind_GetRegionStart  -Wl,--wrap=_Unwind_GetDataRelBase  -Wl,--wrap=_Unwind_GetTextRelBase  -Wl,--wrap=_Unwind_SetIP  -Wl,--wrap=_Unwind_SetGR  -Wl,--wrap=_Unwind_GetLanguageSpecificData  -Wl,--wrap=_Unwind_FindEnclosingFunction  -Wl,--wrap=_Unwind_Resume  -Wl,--wrap=_Unwind_RaiseException  -Wl,--wrap=_Unwind_DeleteException  -Wl,--wrap=_Unwind_ForcedUnwind  -Wl,--wrap=_Unwind_Resume_or_Rethrow  -Wl,--wrap=_Unwind_Backtrace  -Wl,--wrap=__cxa_call_unexpected  -Wl,--wrap=__gxx_personality_v0  -u __cxa_guard_dummy  -lstdc++  esp-idf/pthread/libpthread.a  -lgcc  esp-idf/cxx/libcxx.a  -u __cxx_fatal_exception  esp-idf/app_trace/libapp_trace.a  -lgcov  esp-idf/app_trace/libapp_trace.a  -lgcov  -lc && :
/opt/xtensa-esp32-elf-clang/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: esp-idf/rustlib/target/xtensa-esp32-espidf/release/librustlib.a(rustlib-8ed1900ea86a6c48.rand-4de7581c8c2fb914.rand.5x8vszn4-cgu.15.rcgu.o.rcgu.o):(.literal._ZN3std4sync4once4Once9call_once28_$u7b$$u7b$closure$u7d$$u7d$17hd74d63aeb634a063E.llvm.12770143606975383821+0x4): undefined reference to `pthread_atfork'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

I noticed ESP-IDF pthread.c implementation does not implement pthread_atfork. Am I right in assuming there’s nothing I can do ATM? Is it a bug, pending implementation, or can’t be implemented?

In any case, this should probably be caught at compile time rather than link time. If you could point me to the right repository to where report this issue I’d appreciated it.

Источник

esp-rs / rust-build
Goto Github
PK

View Code? Open in Web Editor
NEW

146.0
8.0
31.0
517 KB

Installation tools and workflows for deploying/building Rust fork esp-rs/rust with Xtensa and RISC-V support

License: MIT License

Shell 64.26%
PowerShell 17.20%
Dockerfile 7.61%
C++ 10.94%

rust-build’s Introduction

This repository contains:

Workflows for building a Rust fork esp-rs/rust with Xtensa support
Binary artifacts in Releases
An installation script to locally install a pre-compiled nightly ESP32 toolchain

If you want to know more about the Rust ecosystem on ESP targets, see The Rust on ESP Book chapter

rust-build
- Table of Contents
- Xtensa Installation
  - Download installer
    - Download installer in Bash
    - Download installer in PowerShell
  - Linux and macOS
    - Prerequisites
    - Installation commands
    - Set up the environment variables
    - Arguments
  - Windows x86_64 GNU
    - Prerequisites x86_64 GNU
    - Installation commands for PowerShell
    - Long path limitation
  - Windows x86_64 MSVC
    - Prerequisites x86_64 MSVC
    - Installation commands for PowerShell
    - Set up the environment variables
    - Long path limitation
- RISC-V Installation
- Building projects
  - Cargo first approach
  - Idf first approach
- Using Containers
- Using Dev Containers

Xtensa Installation

Warning

Install scripts from this repository will now be feature freeze. New features will be added to espup, a Rust version of the install scripts.

Download the installer from the Release section.

Download installer

Download installer in Bash

curl -LO https://github.com/esp-rs/rust-build/releases/download/v1.67.0.0/install-rust-toolchain.sh
chmod a+x install-rust-toolchain.sh

Download installer in PowerShell

Invoke-WebRequest 'https://github.com/esp-rs/rust-build/releases/download/v1.67.0.0/Install-RustToolchain.ps1' -OutFile .Install-RustToolchain.ps1

Linux and macOS

The following instructions are specific for the ESP32 and ESP32-S series based on Xtensa architecture.

Instructions for ESP-C series based on RISC-V architecture are described in RISC-V section.

Prerequisites

Linux:

Dependencies (command for Ubuntu/Debian):

apt-get install -y git curl gcc clang ninja-build cmake libudev-dev unzip xz-utils 
python3 python3-pip python3-venv libusb-1.0-0 libssl-dev pkg-config libpython2.7

No prerequisites are needed for macOS.

Installation commands

git clone https://github.com/esp-rs/rust-build.git
cd rust-build
./install-rust-toolchain.sh
. ./export-esp.sh

Run ./install-rust-toolchain.sh --help for more information about arguments.

Installation of different version of the toolchain:

./install-rust-toolchain.sh --toolchain-version 1.67.0.0
. ./export-esp.sh

Set up the environment variables

We need to update environment variables as some of the installed tools are not
yet added to the PATH environment variable, we also need to add LIBCLANG_PATH
environment variable to avoid conflicts with the system Clang. The environment
variables that we need to update are shown at the end of the install script and
stored in an export file. By default this export file is export-esp.sh but can
be modified with the -f|--export-file argument.

We must set the environment variables in every terminal session.

Note
If the export variables are added to the shell startup script, the shell may need to be refreshed.

Arguments

-b|--build-target: Comma separated list of targets [esp32,esp32s2,esp32s3,esp32c3,all]. Defaults to: esp32,esp32s2,esp32s3
-c|--cargo-home: Cargo path.
-d|--toolchain-destination: Toolchain installation folder. Defaults to: <rustup_home>/toolchains/esp
-e|--extra-crates: Extra crates to install. Defaults to: ldproxy cargo-espflash
-f|--export-file: Destination of the export file generated. Defaults to: export-esp.sh
-i|--installation-mode: Installation mode: [install, reinstall, uninstall]. Defaults to: install
-k|--minified-llvm: Use minified LLVM. Possible values: [YES, NO]. Defaults to: YES
-l|--llvm-version: LLVM version.
-m|--minified-esp-idf: [Only applies if using -s|--esp-idf-version]. Deletes some idf folders to save space. Possible values [YES, NO]. Defaults to: NO
-n|--nightly-version: Nightly Rust toolchain version. Defaults to: nightly
-r|--rustup-home: Path to .rustup. Defaults to: ~/.rustup
-s|--esp-idf-version: ESP-IDF branch to install. When empty, no esp-idf is installed. Default: ""
-t|--toolchain-version: Xtensa Rust toolchain version
-x|--clear-cache: Removes cached distribution files. Possible values: [YES, NO]. Defaults to: YES

Windows x86_64 GNU

The following instructions describe deployment with the GNU toolchain. If you’re using Visual Studio with Windows 10 SDK, consider option Windows x86_64 MSVC.

Prerequisites x86_64 GNU

Install MinGW x86_64 e.g., from releases https://github.com/niXman/mingw-builds-binaries/releases and add bin to environment variable PATH

choco install 7zip -y
Invoke-WebRequest https://github.com/niXman/mingw-builds-binaries/releases/download/12.1.0-rt_v10-rev3/x86_64-12.1.0-release-posix-seh-rt_v10-rev3.7z -OutFile x86_64-12.1.0-release-posix-seh-rt_v10-rev3.7z
7z e x86_64-12.1.0-release-posix-seh-rt_v10-rev3.7z
$env:PATH+=";.....x86_64-12.1.0-release-posix-seh-rt_v10-rev3mingw64bin"

Install ESP-IDF using Windows installer https://dl.espressif.com/dl/esp-idf/

Installation commands for PowerShell

Activate ESP-IDF PowerShell and enter following command:

git clone https://github.com/esp-rs/rust-build.git
cd rust-build
./Install-RustToolchain.ps1 -DefaultHost x86_64-pc-windows-gnu -ExportFile Export-EspRust.ps1
. ./Export-EspRust.ps1

Long path limitation

Several build tools have problem with long paths on Windows including Git and CMake. We recommend to put project on short path or use command subst to map the directory with the project to separate disk letter.

subst "R:" "rust-project"

Windows x86_64 MSVC

The following instructions are specific for the ESP32 and ESP32-S series based on Xtensa architecture. If you do not have Visual Studio and Windows 10 SDK installed, consider the alternative option Windows x86_64 GNU.

Instructions for ESP-C series based on RISC-V architecture are described in RISC-V section.

Prerequisites x86_64 MSVC

Installation of prerequisites using Winget:

winget install --id Git.Git
winget install Python # requirements for ESP-IDF based development, skip in case of Bare metal
winget install -e --id Microsoft.WindowsSDK
winget install Microsoft.VisualStudio.2022.BuildTools --silent --override "--wait --quiet --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64"

Installation of prerequisites using Visual Studio installer GUI — installed with option Desktop development with C++ — components: MSVCv142 — VS2019 C++ x86/64 build tools, Windows 11 SDK

Installation of MSVC and Windows 11 SDK using vs_buildtools.exe:

Invoke-WebRequest 'https://aka.ms/vs/17/release/vs_buildtools.exe' -OutFile .vs_buildtools.exe
.vs_BuildTools.exe --passive --wait --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.VisualStudio.Component.Windows10SDK.20348

Installation of prerequisites using Chocolatey (run PowerShell as Administrator):

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
choco install visualstudio2022-workload-vctools windows-sdk-10.0 -y
choco install cmake git ninja python3 -y  # requirements for ESP-IDF based development, skip in case of Bare metal

Installation commands for PowerShell

git clone https://github.com/esp-rs/rust-build.git
cd rust-build
./Install-RustToolchain.ps1

Export variables are displayed at the end of the output from the script.

Installation of different versions of toolchain:

./Install-RustToolchain.ps1 -ToolchainVersion 1.67.0.0
. ./Export-EspRust.ps1

Set up the environment variables

We need to update environment variables as some of the installed tools are not
yet added to the PATH environment variable, we also need to add LIBCLANG_PATH
environment variable to avoid conflicts with the system Clang. The environment
variables that we need to update are stored in an export file. By default this
export file is Export-EspRust.ps1 but can be modified with the -ExportFile argument.

We must set the environment variables in every terminal session.

Note
If the export variables are added to the shell startup script, the shell may need to be refreshed.

Long path limitation

subst "R:" "rust-project"

RISC-V Installation

The following instructions are specific for ESP32-C based on RISC-V architecture.

Install the RISC-V target for Rust:

rustup target add riscv32imc-unknown-none-elf

Building projects

Cargo first approach

Install cargo-generate
```
cargo install cargo-generate
```

Generate project from template with one of the following templates

# STD Project
cargo generate https://github.com/esp-rs/esp-idf-template cargo
# NO-STD (Bare-metal) Project
cargo generate -a esp-rs/esp-template

To understand the differences between the two ecosystems, see Ecosystem Overview chapter of the book. There is also a Chapter that explains boths template projects:

std template explanation
no_std template explanation

Build and flash:

Where SERIAL is the serial port connected to the target device.

cargo-espflash also allows opening a serial monitor after flashing with --monitor option.

If no SERIAL argument is used, cargo-espflash will print a list of the connected devices, so the user can choose
which one to flash.

See Usage section for more information about arguments.

If espflash is installed (cargo install espflash), cargo run will build, flash the device, and open a serial monitor.

If you are looking for inspiration or more complext projects see:

Awesome ESP Rust — Projects Section
Rust on ESP32 STD demo app

Idf first approach

When building for Xtensa targets, we need to override the esp toolchain, there are several solutions:
— Set esp toolchain as default: rustup default esp
— Use cargo +esp
— Override the project directory: rustup override set esp
— Create a file called rust-toolchain.toml or rust-toolchain with:
toml [toolchain] channel = "esp"

Get example source code

git clone https://github.com/espressif/rust-esp32-example.git
cd rust-esp32-example-main

Select architecture for the build
```
idf.py set-target <TARGET>
```
Where TARGET can be:
- esp32 for the ESP32(Xtensa architecture). [Default]
- esp32s2 for the ESP32-S2(Xtensa architecture).
- esp32s3 for the ESP32-S3(Xtensa architecture).
Build and flash

Using Containers

Alternatively, some container images with pre-installed Rust and ESP-IDF, are published to Dockerhub and can be used to build Rust projects for ESP boards:

idf-rust
Some tags contain only the toolchain. The naming convention for those tags is: <xtensa-version>
Some tags contain full std environment with esp-idf installed, wokwi-server
and web-flash to use them
in Dev Containers. This tags are generated for linux/arm64 and linux/amd64,
and use the following naming convention: <board>_<esp-idf>_<xtensa-version>
Some tags contain full no_stdenvironment, wokwi-server
and web-flash to use them
in Dev Containers. This tags are generated for linux/arm64 and linux/amd64,
and use the following naming convention: <board>_<xtensa-version>
idf-rust-examples — includes two examples: rust-esp32-example and rust-esp32-std-demo.

Podman example with mapping multiple /dev/ttyUSB from host computer to the container:

podman run --device /dev/ttyUSB0 --device /dev/ttyUSB1 -it docker.io/espressif/idf-rust-examples

Docker (does not support flashing from a container):

docker run -it espressif/idf-rust-examples

If you are using the idf-rust-examples image, instructions will be displayed on the screen.

Using Dev Containers

Dev Container support is offered for VS Code, Gitpod, and GitHub Codespaces,
resulting in a fully working environment to develop for ESP boards in Rust,
flash and simulate projects with Wokwi from the container.

Template projects esp-template and
esp-idf-template include a question for Dev Containers support.

rust-build’s People

rust-build’s Issues

Ubuntu 22.04 is using openSSL 3.0 as default

When I install newest Ubuntu 22.04, I found that the version of openssl is 3.0. SO I occur the problem with rust-build.

~/.rustup/toolchains/esp-1.60.0.1/bin/cargo: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Now I get a new Solution that compile the openssl 1.1.1. And add compiled openssl 1.1.1 to ld.so.conf. Can solve the problem temproarily.

Installing riscv32imc-esp-espidf does not work on Apple M1

I’m going through the esp-rs book trying to get a simple example working for my ESP32C3, but I’m unable to install the toolchain:

$ rustup target add riscv32imc-esp-espidf
error: toolchain 'nightly-aarch64-apple-darwin' does not contain component 'rust-std' for target 'riscv32imc-esp-espidf'
note: not all platforms have the standard library pre-compiled: https://doc.rust-lang.org/nightly/rustc/platform-support.html
help: consider using `cargo build -Z build-std` instead

I’m new-ish to Rust, so I’m not sure exactly how to avail myself of the «help» suggestion. Running cargo build -Z build-std shows

error: could not find `Cargo.toml` in `$PWD` or any parent directory

I checked the README of this repo and there is a link to a ESP32C3 document, but the link is broken (it leads to a 404).

Mention in docs that rustup installed through snap has different paths set and creates issues

Hey!
I’m new to rust and was on to trying to replace some of my esp32 coding on arduino IDE with rust. I tried following this guide, but ran into trouble that I now resolved by installing rustup not via snap, but manually. Apparently the snap version of rustup stores its data somewhere else and therefore the default paths do not match well with the defaults set here.

Maybe it’s enough for the next person to stumble upon this issue. I did not work out the snap paths but installed it manually instead, making it work instantly.

Cheers and keep up the good work :).

Shrink LLVM artifact to minimal size

Rust compiler does not need whole llvm-project artifact.
Smaller artifact can make images and deployment smaller which leads to quick container spin-up and smaller footprint in registries.
Research options to shrink the artifact.

Remove PIP_USER=»yes»

Remove workaround PIP_USER="yes", because solution is now part of ESP-IDF:
espressif/esp-idf#7910

This environment variable was set on GitPod build machines and it was not possible to bootstrap the environment for ESP-IDF. The solution was applied to all release branches of ESP-IDF.

riscv32imc-unknown-none-elf is not recognized by +esp toolchain

cd esp32c3-hal/examples/empty
cargo +esp-1.56.0.1 build
error[E0463]: can't find crate for `core`
  |
  = note: the `riscv32imc-unknown-none-elf` target may not be installed

While classical night works:

cargo build
Finished dev [unoptimized + debuginfo] target(s) in 10.94s

I would expect, that our toolchain is able to process the same build.
Adding the target to our toolchain does not work:

rustup target add riscv32imc-unknown-none-elf --toolchain +esp-1.56.0.1
error: toolchain '+esp-1.56.0.1' does not support components: +esp-1.56.0.1 is a custom toolchain

It seems that we need to turn on component support.

SIGABRT: Failed to compile `clap v2.34.0` (on `rust-esp32-std-demo`)

Cloning the example and compiling on macOS Monterey 12.0.1 with the esp toolchain fails when building clap v2.34.0:

error: could not compile `clap`

Caused by:
  process didn't exit successfully: `rustc --crate-name clap --edition=2018 /Users/thorcorreia/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.34.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C split-debuginfo=unpacked -C debuginfo=2 --cfg 'feature="ansi_term"' --cfg 'feature="atty"' --cfg 'feature="color"' --cfg 'feature="default"' --cfg 'feature="strsim"' --cfg 'feature="suggestions"' --cfg 'feature="vec_map"' -C metadata=ac26a8e48a625ff4 -C extra-filename=-ac26a8e48a625ff4 --out-dir /Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps -L dependency=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps --extern ansi_term=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libansi_term-7bb5c8085badc50a.rmeta --extern atty=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libatty-02f4983f38003a7d.rmeta --extern bitflags=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libbitflags-45b4e505e2497911.rmeta --extern strsim=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libstrsim-2b74c9109d8bb938.rmeta --extern textwrap=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libtextwrap-9684b827efe0b904.rmeta --extern unicode_width=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libunicode_width-d208e9921c947bc5.rmeta --extern vec_map=/Users/thorcorreia/Dev/rust-esp32-std-demo/target/debug/deps/libvec_map-63037abaf65b04ec.rmeta --cap-lints allow` (signal: 6, SIGABRT: process abort signal)

It appears that the esp toolchain is unable to compile clap for some reason.

Edit: running the rustc command yields:

rustc(41908,0x7000083ca000) malloc: *** error for object 0x600002596000: pointer being realloc'd was not allocated

Fix shebang in all scripts

Please replace all occurences of #!/usr/bin/ with #!/usr/bin/env . This is more compatible.

Incomplete installation instructions and script issue

Hello,

First, thanks a lot for the effort to get Rust working for Espressif devices. These are suggestions to have the installation process a bit smoother.

Installation instructions

From the installation instruction, it is not clear whether the ESP-IDF framework needs to be installed or not and which version is supported. When trying the command idf.py set-target esp32, the system can’t find it. There must be something lacking in the exports for the PATH.

End of script update to .zshrc

I’m using Ubuntu 20.4. Bash is the standard shell. As there are no .zshrc in the user’s main folder, the updates on PATH and other env variables are not done. It would be handy to have the .bashrc and .profile automatically updated in this context. Or say so in some output text to help newbies like me do it by hand.

Thanks again!
Guy

Install extra crate with cargo if no binary package is available

Atomic operations unavaliable on esp8266 chips

When compiling with the toolchain installed through this tool, any code that uses the atomic instructions for fetch_add or other similar ones the linker will error out

undefined reference to `__sync_fetch_and_add_4′

Through much searching I am unable to track down where or how I would inform the linker of these symbols or where in my installation I am missing something that would provide them. Atomic operations like store and load seem to work fine, but it is weird that the fetch_and_... types are missing and does not seem to be documented anywhere

Support for ESP-IDF v5.0 CI

ESP-IDF v5.0 should become available mid-summer 2022.
Make sure that build works well with Rust.

Cargo binary for macOS assumes OpenSSL is installed via Homebrew

When following the instructions to install the toolchain on macOS, the cargo that gets installed links to OpenSSL via the openssl-sys crate and has library paths that assume OpenSSL was installed via Homebrew.

This leads to the following error if OpenSSL is installed by, for example, MacPorts.

$ cargo +esp
dyld: Library not loaded: /usr/local/opt/[email protected]/lib/libssl.1.1.dylib
  Referenced from: /Users/steve/.rustup/toolchains/esp/bin/cargo
  Reason: image not found
Abort trap: 6

This can be fixed using install_name_tool(1).

$ install_name_tool -change /usr/local/opt/[email protected]/lib/libssl.1.1.dylib /opt/local/lib/libssl.3.dylib 
                    -change /usr/local/opt/[email protected]/lib/libcrypto.1.1.dylib /opt/local/lib/libcrypto.3.dylib 
                    cargo

This allows cargo to run, but the libraries have different compatibility versions so I’m not sure any OpenSSL functions would actually work correctly or not.

Use released binary if installing `cargo-generate`

Generate several tags for espressif/idf-rust Dockerhub image

Add CI, similar to the one in esp-rs-container, to publish in espressif/idf-rust several tags with different esp-idf versions and different boards installed. Tags should be available in linux/amd64 and linux/arm64.

For tags, the naming will be the following: <boards>_<xtensa>_<esp-idf>, where :

Boards installed in esp-idf: esp32, esp32c3, esp32s2, esp32s3 or all
Rust Xtensa toolchain version
Esp-Idf version: release/v4.4, master(v5.0)….

Installer breaks when `-n` is empty

When using the installer to install the toolchain, setting the --nightly-version to an empty value (-n "") causes the NIGHTLY_VERSION env var not to be set, in turn causing the installation to fail at this point, because the argument to install_rust_toolchain is empty although it is required.

Is this intended behavior?

No usable xtensa compiler is installed

The recent merge and release of 0549a1a has disabled the installation of gcc while also not installing any usable other compilers for xtensa. The installation of Clang uses a custom minimal build with only libs and no binaries. I think rust-build should just use the upstream Clang compiler which could reduce complexity (as it’d just depend on upstream).

This ties in with my earlier observation in #85.

At the same time, there are still some unused gcc variables left in the installation script.

Research dependency of toolchains nightly and stable

Right now we deploy stable, nightly and our toolchain for building ESP32 target.
Investigate, whether this is really necessary and whether the build can work even without nightly and stable.
Verify changes by running test-rust-installer.sh.

Build Rust Toolchain on GitHub Windows 2022 runner — using shorter paths with subst

Problem with long paths on Windows GitHub runner could be solved by following workaround:

 - name: Map local long path to new drive
        id: map_path
        shell: pwsh
        run: subst "p:" "$env:GITHUB_WORKSPACE"

Update ldproxy url

Since esp-rs/embuild/pull/49 just got merged, we should update the URL being used in the install script

Error compiling some libraries with toolchain

Hello.

I am currently trying to use the library x25519-dalek for a project that needs to run on a ESP32. This means that we have no operating system and no STD. But the library should be in the category «No standard library» which should be fine for me in this case.

I am using this build chain, however it decides to give me an error.

But when attempting to build it I recieve the following error:

error: linking with `ldproxy` failed: exit status: 1
...
  = note: Running ldproxy
          Error: Linker /home/carl/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/bin/xtensa-esp32-elf-gcc failed: exit status: 1
          STDERR OUTPUT:
          /home/carl/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/carl/Documents/git/github/esp-rs/esp32-build/target/xtensa-esp32-espidf/debug/deps/libclear_on_drop-7f6bb154f7984c2b.rlib: error adding symbols: file format not recognized
          collect2: error: ld returned 1 exit status

full log here

And the project I am running and failing the build is this — The following line is what triggers this error

Hope this is something you can help me with.

Add install-rust-toolchain.sh to release artifacts

I think it would be helpful to add the install-rust-toolchain.sh installer script to the release artifacts. This would make it easier to automate the process of installing the binary toolchains by simply downloading and then running the installer script. This would allow individual users to install the toolchain without needing to check out the source repository first.

Path to CLANG contains extra directory for aarch64 linux

Add clippy

Request: add clippy back to the binary release as compiling from source depends on rustc-dev crate which as well is not distributed at the moment. Using clippy from the default toolchain causes the problem that it is not working together with —target

Add a flag to the installation script to disable installing `cargo-espflash`

I’m using the installation script from this repository for the xtensa-toolchain action, which does not need cargo-espflash installed. This only increases the run time of the action, which I’m trying to minimize.

It would be nice to have a flag which would allow me to disable the installation of cargo-espflash. I am able to do so with ldproxy already, for example.

Export path to clang’s bin dir doesn’t exist anymore with llvm 14

If you investigate the extracted LLVM dirs in .espressif/tools, you’ll notice that LLVM 14 doesn’t have a bin/ dir anymore.

cd ~/.espressif/tools
❯ ls xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu 
bin/  include/  lib/  libexec/  share/  xtensa-esp32-elf/
~/.espressif/tools 
❯ ls xtensa-esp32-elf-clang/esp-14.0.0-20220415-x86_64-unknown-linux-gnu/lib 
clang/  [email protected]  [email protected]  libclang.so.14.0.0*

As we can see, what was once the LLVM dir is now merely the contents of the former lib/ dir. However, the path to the now non-existent bin/ is still being exported.

Not sure what the right way to fix this is. Stop exporting the PATH to clang’s bin? Download a different LLVM release?

Installation script pollutes executing directory with installation artifacts

This isn’t really a big deal, but would be nice if the installation script cleaned up after itself. Very much a «nice to have» feature. Currently following installation via the script, the following files and directories still exist in the executing directory:

[email protected] ~/temp
λ ll                                                                                                                                                                                                                                                                                                                                                               2022-04-07 09:27:36
total 170400
-rwxr-xr-x   1 jesse  staff   8.4K  7 Apr 09:01 install-rust-toolchain.sh*
drwxr-xr-x  17 jesse  staff   544B  7 Apr 09:02 rust-1.60.0.0-x86_64-apple-darwin/
-rw-r--r--   1 jesse  staff    80M  7 Apr 09:02 rust-1.60.0.0-x86_64-apple-darwin.tar.xz
drwxr-xr-x  12 jesse  staff   384B  7 Apr 09:02 rust-src-1.60.0.0/
-rw-r--r--   1 jesse  staff   2.6M  7 Apr 09:02 rust-src-1.60.0.0.tar.xz

Check cargo-espflash version during installation

Check whether cargo-espflash has new version.
cargo install might fail on following error which results in keeping previous version e.g. v1.1.0

cargo install cargo-espflash
    Updating crates.io index
  Downloaded cargo-espflash v1.2.0
  Downloaded 1 crate (23.7 KB) in 0.35s
error: binary `cargo-espflash.exe` already exists in destination
Add --force to overwrite

./install-rust-toolchain.sh: line 81: ./rust-src-1.55.0-dev/install.sh: No such file or directory

Just tried to reinstall rust toolchain.

./install-rust-toolchain.sh                                                                                                                                             
/Users/andres/.cargo/bin/rustc
rustfmt 1.4.37-stable (09c42c45 2021-10-18)
Installation of toolchain for x86_64-apple-darwin
** downloading: https://github.com/esp-rs/rust-build/releases/download/v1.55.0-dev/rust-1.55.0-dev-x86_64-apple-darwin.tar.xz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   650  100   650    0     0   1577      0 --:--:-- --:--:-- --:--:--  1573
100  141M  100  141M    0     0  5682k      0  0:00:25  0:00:25 --:--:-- 5852k
install: creating uninstall script at /Users/andres/.rustup/toolchains/esp/lib/rustlib/uninstall.sh
install: installing component 'rustc'
install: installing component 'cargo'
install: installing component 'clippy-preview'
install: installing component 'rls-preview'
install: installing component 'rust-analyzer-preview'
install: installing component 'miri-preview'
install: installing component 'rustfmt-preview'
install: installing component 'llvm-tools-preview'
install: installing component 'rust-analysis-x86_64-apple-darwin'
install: installing component 'rust-std-x86_64-apple-darwin'

    rust installed.

./install-rust-toolchain.sh: line 81: ./rust-src-1.55.0-dev/install.sh: No such file or directory

ls -ltr                                                                                                                                                        49s  ●  ~/D/y/rust-build
total 238424
drwxr-xr-x 21 andres staff       672 Sep 15 17:39 rust-1.55.0-dev-x86_64-apple-darwin
-rw-r--r--  1 andres staff       324 Oct 20 15:44 Dockerfile
-rw-r--r--  1 andres staff      3488 Oct 20 15:44 Install-RustToolchain.ps1
-rw-r--r--  1 andres staff      1063 Oct 20 15:44 LICENSE
-rw-r--r--  1 andres staff      3362 Oct 20 15:44 README.md
-rwxr-xr-x  1 andres staff      3579 Oct 20 15:44 install-rust-toolchain.sh
drwxr-xr-x  3 andres staff        96 Oct 20 15:44 support
-rw-r--r--  1 andres staff   2429160 Oct 20 15:50 rust-src-1.55.0-dev.tar.xz
-rw-r--r--  1 andres staff  89895320 Oct 20 15:52 xtensa-esp32-elf-llvm12_0_1-esp-12.0.1-20210823-macos.tar.xz
-rw-r--r--  1 andres staff     21569 Oct 20 16:18 main.zip
-rw-r--r--  1 andres staff 148715876 Oct 22 16:14 rust-1.55.0-dev-x86_64-apple-darwin.tar.xz

Rust toolchain mirror on dl.espressif.com

Setup Rust toolchain mirror, so that toolchain is accessible also in case when github.com is not reachable

Simpler deployment of Rust toolchain with LLVM

It’s not possible to use rustup to deploy custom toolchain from custom location. It’s know limitation. More details: esp-rs/rust#72

Prepare a solution which makes it simpler and safer to install custom Rust toolchain.

Build multiple examples to verify integrity of the toolchain

Allow `—build-target all`

Allow parameter all for -b|--build-target argument to install both nightly and esp toolchain and, if some version of -s|--esp-idf-version is specified, install it for all boards.

If `$CARGO_HOME` is set, installation script tries to source potentially non-existent file

The script currently does this:

        if [ ! -z "${CARGO_HOME}" ]; then
            source ${CARGO_HOME}/env
        else

So it assumes that ${CARGO_HOME}/env exists just because ${CARGO_HOME} is set. This crashes my current environment and I have to create a env file just for this script not to choke. It’d be nice if the script also checked for actual existence of that file before blindly sourcing it.

set release-channel=nightly for builds

We should set --release-channel=nightly when configuring our compiler builds. I.e ./configure --experimental-targets=Xtensa --release-channel=nightly

Before:

rustc +esp-dev --version --verbose
rustc 1.59.0 (04e60933c 2022-03-14)
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.0

After:

rustc +esp-dev --version --verbose
rustc 1.59.0 (04e60933c 2022-03-14)
binary: rustc
commit-hash: 04e60933cbe54af30d339efd67da6b43016433ad
commit-date: 2022-03-14
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.0

Unable to build `rust-esp32-std-demo` using Docker and cargo

Hello!

I seem unable to build rust-esp32-std-demo using the Docker image espressif/idf-rust-examples:latest (image ID 562dd6cc6e54) using cargo. The issue seems to be related to PlatformIO. Builds using idf.py build work fine.

The host machine is an Intel-Mac running macOS Big Sur v11.2.3.

Suggestions?

Relevant logs:

docker run -it espressif/idf-rust-examples
Detecting the Python interpreter
Checking "python" ...
Python 3.8.10
"python" has been detected
Adding ESP-IDF tools to PATH...
Not using an unsupported version of tool xtensa-esp32-elf found in PATH: esp-2021r1-8.4.0.
Using Python interpreter in /opt/esp/python_env/idf5.0_py3.8_env/bin/python
Checking if Python packages are up to date...
Python requirements from /opt/esp/idf/requirements.txt are satisfied.
Added the following directories to PATH:
  /opt/esp/idf/components/esptool_py/esptool
  /opt/esp/idf/components/espcoredump
  /opt/esp/idf/components/partition_table
  /opt/esp/idf/components/app_update
  /opt/esp/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin
  /opt/esp/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin
  /opt/esp/tools/xtensa-esp32s3-elf/esp-2021r2-8.4.0/xtensa-esp32s3-elf/bin
  /opt/esp/tools/riscv32-esp-elf/esp-2021r2-8.4.0/riscv32-esp-elf/bin
  /opt/esp/tools/esp32ulp-elf/2.28.51-esp-20191205/esp32ulp-elf-binutils/bin
  /opt/esp/tools/esp32s2ulp-elf/2.28.51-esp-20191205/esp32s2ulp-elf-binutils/bin
  /opt/esp/tools/cmake/3.20.3/bin
  /opt/esp/tools/openocd-esp32/v0.10.0-esp32-20211111/openocd-esp32/bin
  /opt/esp/python_env/idf5.0_py3.8_env/bin
  /opt/esp/idf/tools
Done! You can now compile ESP-IDF projects.
Go to the project directory and run:

  idf.py build

==============================================================================
=           Docker image with ESP-IDF, Rust compiler and examples            =
=              https://github.com/espressif/rust-esp32-example               =
==============================================================================

Available examples:

* "cargo-first" approach
  `` ``` ``sh
    cd /opt/rust-esp32-std-demo
    cargo +esp build --release
    espflash /dev/ttyUSB0 target/xtensa-esp32-espidf/release/rust-esp32-std-demo
    cargo pio espidf monitor -e release /dev/ttyUSB0
  `` ``` ``

* "idf.py-first" approach - integration via CMake files
  `` ``` ``sh
    cd /opt/rust-esp32-example
    idf.py build
  `` ``` ``
[email protected]:/opt# cd rust-esp32-std-demo
[email protected]:/opt/rust-esp32-std-demo# export set RUST_BACKTRACE=1 && cargo +esp build --release
warning: unused config key `unstable.configurable-env` in `/opt/rust-esp32-std-demo/.cargo/config.toml`
warning: unused config key `unstable.extra-link-arg` in `/opt/rust-esp32-std-demo/.cargo/config.toml`
   Compiling compiler_builtins v0.1.49
   Compiling core v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/core)
   Compiling libc v0.2.103
   Compiling cc v1.0.69
   Compiling std v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/std)
   Compiling libc v0.2.109
   Compiling memchr v2.4.1
   Compiling proc-macro2 v1.0.33
   Compiling unicode-xid v0.2.2
   Compiling syn v1.0.82
   Compiling cfg-if v1.0.0
   Compiling cc v1.0.72
   Compiling log v0.4.14
   Compiling autocfg v1.0.1
   Compiling serde_derive v1.0.130
   Compiling serde v1.0.130
   Compiling fnv v1.0.7
   Compiling once_cell v1.8.0
   Compiling ryu v1.0.6
   Compiling spin v0.5.2
   Compiling untrusted v0.7.1
   Compiling regex-syntax v0.6.25
   Compiling serde_json v1.0.72
   Compiling version_check v0.9.3
   Compiling anyhow v1.0.51
   Compiling tinyvec_macros v0.1.0
   Compiling glob v0.3.0
   Compiling crossbeam-utils v0.8.5
   Compiling matches v0.1.9
   Compiling lazy_static v1.4.0
   Compiling adler v1.0.2
   Compiling ppv-lite86 v0.2.15
   Compiling gimli v0.26.1
   Compiling unicode-width v0.1.9
   Compiling bitflags v1.3.2
   Compiling percent-encoding v2.1.0
   Compiling same-file v1.0.6
   Compiling unicode-bidi v0.3.7
   Compiling ansi_term v0.12.1
   Compiling vec_map v0.8.2
   Compiling termcolor v1.1.2
   Compiling rustc-demangle v0.1.21
   Compiling bindgen v0.57.0
   Compiling humantime v2.1.0
   Compiling strsim v0.8.0
   Compiling shlex v0.1.1
   Compiling itoa v0.4.8
   Compiling peeking_take_while v0.1.2
   Compiling lazycell v1.3.0
   Compiling zero v0.1.2
   Compiling either v1.6.1
   Compiling chunked_transfer v1.4.0
   Compiling base64 v0.13.0
   Compiling rustc-hash v1.1.0
   Compiling remove_dir_all v0.5.3
   Compiling unicode-segmentation v1.8.0
   Compiling shlex v1.1.0
   Compiling futures-core v0.3.18
   Compiling strsim v0.10.0
   Compiling ident_case v1.0.1
   Compiling az v1.2.0
   Compiling async-trait v0.1.51
   Compiling paste v1.0.6
   Compiling heapless v0.7.8
   Compiling unwind v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/unwind)
   Compiling libloading v0.7.2
   Compiling cmake v0.1.46
   Compiling backtrace v0.3.63
   Compiling ring v0.16.20
   Compiling miniz_oxide v0.4.4
   Compiling num-traits v0.2.14
   Compiling thread_local v1.1.3
   Compiling rustc-std-workspace-core v1.99.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/rustc-std-workspace-core)
   Compiling nom v5.1.2
   Compiling tinyvec v1.5.1
   Compiling clang-sys v1.3.0
   Compiling textwrap v0.11.0
   Compiling form_urlencoded v1.0.1
   Compiling walkdir v2.3.2
   Compiling addr2line v0.17.0
   Compiling xmas-elf v0.8.0
   Compiling heck v0.3.3
   Compiling unicode-normalization v0.1.19
   Compiling getrandom v0.2.3 (https://github.com/esp-rs-compat/getrandom.git#b8cb133e)
   Compiling atty v0.2.14
   Compiling dirs-sys v0.3.6
   Compiling which v3.1.1
   Compiling which v4.2.2
   Compiling remove_dir_all v0.7.0
   Compiling aho-corasick v0.7.18
   Compiling bstr v0.2.17
   Compiling object v0.27.1
   Compiling quote v1.0.10
   Compiling alloc v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/alloc)
   Compiling cfg-if v0.1.10
   Compiling rand_core v0.6.3
   Compiling clap v2.34.0
   Compiling dirs v4.0.0
   Compiling idna v0.2.3
   Compiling regex v1.5.4
   Compiling rustc-std-workspace-alloc v1.99.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/rustc-std-workspace-alloc)
   Compiling panic_abort v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/panic_abort)
   Compiling webpki v0.22.0
   Compiling sct v0.7.0
   Compiling cexpr v0.4.0
   Compiling rand_chacha v0.3.1
   Compiling url v2.2.2
   Compiling globset v0.4.8
   Compiling env_logger v0.8.4
   Compiling darling_core v0.13.0
   Compiling panic_unwind v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/panic_unwind)
   Compiling std_detect v0.1.5 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/stdarch/crates/std_detect)
   Compiling hashbrown v0.11.0
   Compiling webpki-roots v0.22.1
   Compiling rustls v0.20.2
   Compiling rand v0.8.4
   Compiling ignore v0.4.18
   Compiling strum_macros v0.21.1
   Compiling thiserror-impl v1.0.30
   Compiling derivative v2.2.0
   Compiling ureq v2.3.1
   Compiling darling_macro v0.13.0
   Compiling tempfile v3.2.0
   Compiling globwalk v0.8.1
   Compiling strum v0.21.0
   Compiling thiserror v1.0.30
   Compiling proc_macro v0.0.0 (/opt/rustup/toolchains/esp/lib/rustlib/src/rust/library/proc_macro)
   Compiling darling v0.13.0
   Compiling nb v1.0.0
   Compiling void v1.0.2
   Compiling cache-padded v1.1.1
   Compiling waker-fn v1.1.0
   Compiling byteorder v1.4.3
   Compiling parking v2.0.0
   Compiling futures-io v0.3.18
   Compiling pin-project-lite v0.2.7
   Compiling fastrand v1.5.0
   Compiling event-listener v2.5.1
   Compiling display-interface v0.4.1
   Compiling async-task v4.0.3
   Compiling base64 v0.12.3
   Compiling slab v0.4.5
   Compiling atomic-waker v1.0.0
   Compiling mutex-trait v0.2.0
   Compiling byte-slice-cast v0.3.5
   Compiling cty v0.2.2
   Compiling stable_deref_trait v1.2.0
   Compiling micromath v1.1.1
   Compiling toml v0.5.8
   Compiling enumset_derive v0.5.5
   Compiling socket2 v0.4.2 (https://github.com/esp-rs-compat/socket2#7217ebe8)
   Compiling nb v0.1.3
   Compiling concurrent-queue v1.2.2
   Compiling hash32 v0.2.1
   Compiling no-std-net v0.5.0
   Compiling futures-lite v1.12.0
   Compiling async-lock v2.4.0
   Compiling http-auth-basic v0.1.3
   Compiling embedded-graphics-core v0.3.3
   Compiling cstr_core v0.2.4
   Compiling float-cmp v0.8.0
   Compiling cargo_toml v0.9.2
   Compiling proc-macro-crate v1.1.0
   Compiling enumset v1.0.8
   Compiling polling v2.1.0 (https://github.com/esp-rs-compat/polling#260dded7)
   Compiling embedded-hal v0.2.6
   Compiling async-channel v1.6.1
   Compiling async-executor v1.4.1
   Compiling embedded-graphics v0.7.1
   Compiling embuild v0.25.4
   Compiling num_enum_derive v0.5.4
   Compiling async-io v1.6.0
   Compiling display-interface-i2c v0.4.0
   Compiling display-interface-spi v0.4.1
   Compiling ili9341 v0.5.0 (https://github.com/yuri91/ili9341-rs#8aeefc4a)
   Compiling blocking v1.1.0
   Compiling st7789 v0.6.1
   Compiling num_enum v0.5.4
   Compiling ssd1306 v0.7.0
   Compiling esp-idf-sys v0.27.0
   Compiling esp-idf-hal v0.27.0
   Compiling esp-idf-svc v0.32.3
   Compiling rust-esp32-std-demo v0.20.6 (/opt/rust-esp32-std-demo)
   Compiling async-fs v1.5.0
   Compiling async-net v1.6.1
   Compiling embedded-svc v0.15.3
   Compiling smol v1.2.5 (https://github.com/esp-rs-compat/smol#b9a770e7)
error: failed to run custom build command for `esp-idf-sys v0.27.0`

Caused by:
  process didn't exit successfully: `/opt/rust-esp32-std-demo/target/release/build/esp-idf-sys-4c914487a370c77f/build-script-build` (exit status: 1)
  --- stdout
  Installer version: 1.0.2
  Platform: Linux-5.10.47-linuxkit-x86_64-with-glibc2.29
  Python version: 3.8.10 (default, Sep 28 2021, 16:10:42) 
  [GCC 9.3.0]
  Python path: /opt/esp/python_env/idf5.0_py3.8_env/bin/python3
  Creating a virtual environment at /root/.platformio/penv
  Updating Python package manager (PIP) in a virtual environment
  PIP has been successfully updated!
  Virtual environment has been successfully created!
  Installing PlatformIO Core
  Collecting platformio
    Downloading platformio-5.2.4.tar.gz (219 kB)
    Preparing metadata (setup.py): started
    Preparing metadata (setup.py): finished with status 'done'
  Collecting bottle==0.12.*
    Using cached bottle-0.12.19-py3-none-any.whl (89 kB)
  Collecting click!=8.0.2,<9,>=8
    Using cached click-8.0.3-py3-none-any.whl (97 kB)
  Collecting colorama
    Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
  Collecting marshmallow<4,>=2
    Using cached marshmallow-3.14.1-py3-none-any.whl (47 kB)
  Collecting pyelftools<1,>=0.27
    Using cached pyelftools-0.27-py2.py3-none-any.whl (151 kB)
  Collecting pyserial==3.*
    Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
  Collecting requests==2.*
    Using cached requests-2.26.0-py2.py3-none-any.whl (62 kB)
  Collecting semantic_version==2.8.*
    Using cached semantic_version-2.8.5-py2.py3-none-any.whl (15 kB)
  Collecting tabulate==0.8.*
    Using cached tabulate-0.8.9-py3-none-any.whl (25 kB)
  Collecting zeroconf==0.37.*
    Downloading zeroconf-0.37.0-py3-none-any.whl (105 kB)
  Collecting aiofiles==0.8.*
    Downloading aiofiles-0.8.0-py3-none-any.whl (13 kB)
  Collecting ajsonrpc==1.*
    Using cached ajsonrpc-1.2.0-py3-none-any.whl (22 kB)
  Collecting starlette==0.17.*
    Using cached starlette-0.17.1-py3-none-any.whl (58 kB)
  Collecting uvicorn==0.16.*
    Downloading uvicorn-0.16.0-py3-none-any.whl (54 kB)
  Collecting wsproto==1.0.*
    Using cached wsproto-1.0.0-py3-none-any.whl (24 kB)
  Collecting charset-normalizer~=2.0.0
    Using cached charset_normalizer-2.0.9-py3-none-any.whl (39 kB)
  Collecting urllib3<1.27,>=1.21.1
    Using cached urllib3-1.26.7-py2.py3-none-any.whl (138 kB)
  Collecting certifi>=2017.4.17
    Using cached certifi-2021.10.8-py2.py3-none-any.whl (149 kB)
  Collecting idna<4,>=2.5
    Using cached idna-3.3-py3-none-any.whl (61 kB)
  Collecting anyio<4,>=3.0.0
    Using cached anyio-3.4.0-py3-none-any.whl (78 kB)
  Collecting h11>=0.8
    Using cached h11-0.12.0-py3-none-any.whl (54 kB)
  Collecting asgiref>=3.4.0
    Using cached asgiref-3.4.1-py3-none-any.whl (25 kB)
  Collecting ifaddr>=0.1.7
    Using cached ifaddr-0.1.7-py2.py3-none-any.whl (10 kB)
  Collecting sniffio>=1.1
    Using cached sniffio-1.2.0-py3-none-any.whl (10 kB)
  Building wheels for collected packages: platformio
    Building wheel for platformio (setup.py): started
    Building wheel for platformio (setup.py): finished with status 'done'
    Created wheel for platformio: filename=platformio-5.2.4-py3-none-any.whl size=344394 sha256=e08ce5c25916b31c0479140b215d83dc9897e657b1a1122bf75fbc3947cf894d
    Stored in directory: /root/.cache/pip/wheels/c7/5f/eb/2b681c5612c9a8ace53548f7febbd3edd52d6522ebfe2aafcc
  Successfully built platformio
  Installing collected packages: sniffio, idna, urllib3, ifaddr, h11, click, charset-normalizer, certifi, asgiref, anyio, zeroconf, wsproto, uvicorn, tabulate, starlette, semantic-version, requests, pyserial, pyelftools, marshmallow, colorama, bottle, ajsonrpc, aiofiles, platformio
  Successfully installed aiofiles-0.8.0 ajsonrpc-1.2.0 anyio-3.4.0 asgiref-3.4.1 bottle-0.12.19 certifi-2021.10.8 charset-normalizer-2.0.9 click-8.0.3 colorama-0.4.4 h11-0.12.0 idna-3.3 ifaddr-0.1.7 marshmallow-3.14.1 platformio-5.2.4 pyelftools-0.27 pyserial-3.5 requests-2.26.0 semantic-version-2.8.5 sniffio-1.2.0 starlette-0.17.1 tabulate-0.8.9 urllib3-1.26.7 uvicorn-0.16.0 wsproto-1.0.0 zeroconf-0.37.0

  PlatformIO Core has been successfully installed into an isolated environment `/root/.platformio/penv`!

  The full path to `platformio.exe` is `/root/.platformio/penv/bin/platformio`

  If you need an access to `platformio.exe` from other applications, please install Shell Commands
  (add PlatformIO Core binary directory `/root/.platformio/penv/bin` to the system environment PATH variable):

  See https://docs.platformio.org/page/installation.html#install-shell-commands

  Found compatible PlatformIO Core 5.2.4 -> /root/.platformio/penv/bin/platformio

  --- stderr
  Error: Compatible PlatformIO Core not found.
  Reason: PlatformIO Core was installed using another platform `Linux-5.11.0-1021-azure-x86_64-with-glibc2.29`. Your current platform: Linux-5.10.47-linuxkit-x86_64-with-glibc2.29
  Error: invalid type: null, expected a string at line 1 column 9390

  Stack backtrace:
     0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
     1: <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual
     2: embuild::pio::Pio::json
     3: embuild::pio::Pio::frameworks
     4: embuild::pio::Resolver::resolve_platform_all
     5: embuild::pio::Resolver::resolve
     6: build_script_build::build_driver::build
     7: build_script_build::main
     8: core::ops::function::FnOnce::call_once
     9: std::sys_common::backtrace::__rust_begin_short_backtrace
    10: std::rt::lang_start::{{closure}}
    11: std::rt::lang_start_internal
    12: std::rt::lang_start
    13: main
    14: __libc_start_main
    15: _start

Build Podman/Docker image with Rust compiler on aarch64

Podman/Docker image is available only for x86_64 — docker.io/espressif/idf-rust-examples
Documentation how to use: https://github.com/esp-rs/rust-build/#rust-with-podman-or-docker
Add a version for aarch64, so that servers with these architectures can be used to build the software

It’s not clear if we still need to install ESP-IDF.

Both the esp book and this repository make no mention of requiring esp-idf, but it seems that the linker is still needed.

(It does look like it builds esp-idf, but in my current environment, it fails to build it.)

Request build for windows-gnu

Current toolchain : stable-x86_64-pc-windows-gnu

The only available binary for windows is for msvc toolchain

Stack overflow, despite not doing anything crazy?

Hi, me and my partner have been trying to run our project on a esp32 wroom.

So far, w’re trying to run this project. There is a certain line, where one of our dependencies use serde_cbor to serialize an object, the function looks like this:


    pub fn generate_message_1(
        self,
        r#type: isize,
        suites: isize,
    ) -> Result<(Vec<u8>, PartyI<Msg2Receiver>), EarlyError> {
        // Encode the necessary informati'on into the first message
        let msg_1 = Message1 {
            r#type,
            suite: suites,
            x_i: self.0.x_i.as_bytes().to_vec(), // sending PK as vector
            c_i: self.0.c_i,
        };
        // Get CBOR sequence for message
        let msg_1_seq = util::serialize_message_1(&msg_1)?;
        // Copy for returning
        let msg_1_bytes = msg_1_seq.clone();

        Ok((
            msg_1_bytes,
            PartyI(Msg2Receiver {
                i_ecdh_ephemeralsecret: self.0.secret,
                stat_priv: self.0.static_secret,
                stat_pub: self.0.static_public,
      //          auth: self.0.auth,
                kid: self.0.kid,
                msg_1_seq,
            }),
        ))
    }
}

And the serialization function that is lastly called looks like this:


fn serialize(object: impl Serialize, offset: usize) -> Vec<u8> {
    // Serialize to byte vector
    let mut v = serde_cbor::to_vec(&object).expect("error during serialization");
    // Return everything starting from the offset
    v.drain(offset..).collect()
}

I might not be super helpfull to include the code, but I thought I would do it anyway.

Anyways, this runs with no issues on our own machines, but as soon as we try to flash it onto our ESP32 wroom, this happens:

***ERROR*** A stack overflow in task main has been detected.
Backtrace:0x40081a36:0x3ffb63d00x40084d21:0x3ffb63f0 0x40087476:0x3ffb6410 0x40086309:0x3ffb6490 0x40084e20:0x3ffb64c0 0x40084dd2:0x3ffb64f0 0x400e9735:0x00000004  |<-CORRUPTED
ELF file SHA256: 0000000000000000

We should have 520KB disposable, and in my mind, what we’re doing here should definitely not overflow that.

Is there any configurations that one can do to access more ram on the device? or what is this likely to be caused by? it seems very unlikely to me that what were doing now overfills 520 kb

Installation of espflash fails with error

Error message:

error[E0658]: exclusive range pattern syntax is experimental
  --> /home/georgik/.cargo/registry/src/github.com-1ecc6299db9ec823/espflash-1.1.0/src/chip/esp32/esp32c3.rs:85:53
   |
85 |             (ImageFormatId::DirectBoot, None | Some(3..)) => {

Reason: Version of Rust 1.54. Required version 1.55.

Centralize storage of release number from CI scripts

Problem: Rust toolchain version number is stored in 23 files. Each release requires an update of all these files.

Find a way to reduce repeated magic numbers in CI scripts.

Test scripts — add support for validation on real HW

Add parameters which allows testing the build on real HW.

Update of custom toolchain using rustup

Scenario: User deployed toolchain 1.56.0.0 and later on user wants upgrade to 1.59.0.0
The installation script does not display any warning an quits.

Workaround:

run installation with parameter -i: ./install-rust-toolchain.sh -i reinstall
or delete ~/.rustup/toolchains/esp

Expected behavior: Installer allows updated of the toolchain in the similar way like rustup

Running ./install-rust-toolchain.sh without args results in error

Running plain ./install-rust-toolchain.sh currently results in an error:

./install-rust-toolchain.sh: line 607: : No such file or directory

This is because the EXPORT_FILE is used despite being unset.

Add CC and AR variables of compiler name to generated export script

The variable export script currently has this content more or less:

export PATH="/home/svenstaro/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/bin/:$PATH"
export LIBCLANG_PATH="/home/svenstaro/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/lib/"
export PIP_USER=no

This will currently make build.rs-driven cross-compilation impossible since the CC and AR are unset and so a crate such as cc will still use the host’s regular cc and ar commands.

Consider this simple build.rs:

fn main() -> anyhow::Result<()> {
    println!("cargo:rerun-if-changed=c/hello.c");
    println!("cargo:rerun-if-changed=target/export-esp-rust.sh");
    cc::Build::new()
        .file("c/hello.c")
        .compile("hello");

    embuild::build::CfgArgs::output_propagated("ESP_IDF")?;
    embuild::build::LinkArgs::output_propagated("ESP_IDF")
}

This won’t compile properly as it stands right now because of the aforementioned reason. I suggest expanding the exported variables to include all of the cross compilation toolchain tools.

In fact, I wonder why this is not being done and whether I’m missing something here.

Consider this:

export CC="xtensa-esp32-elf-gcc"
export AR="xtensa-esp32-elf-ar"
export PATH="/home/svenstaro/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/bin/:$PATH"
export LIBCLANG_PATH="/home/svenstaro/.espressif/tools/xtensa-esp32-elf-clang/esp-13.0.0-20211203-x86_64-unknown-linux-gnu/lib/"
export PIP_USER=no

Would allow you to compile and link most simple C programs directly and without further hassle. What do you think?

Rustc 1.56.0.1 fails with SIGABRT on macOS Monterey x86_64

Error:

error: could not compile `core`
Caused by:
  process didn't exit successfully: `rustc --crate-name core --edition=2018 /Users/user/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=1 -C embed-bitcode=no -C debuginfo=2 -C debug-assertions=on --cfg 'feature="panic_immediate_abort"' -C metadata=ebd3b023ebdd7018 -C extra-filename=-ebd3b023ebdd7018 --out-dir /Users/user/Workspace/ESP32/esp32-hello-rust/rustlib/target/xtensa-esp32-none-elf/debug/deps --target xtensa-esp32-none-elf -Z force-unstable-if-unmarked -L dependency=/Users/user/Workspace/ESP32/esp32-hello-rust/rustlib/target/xtensa-esp32-none-elf/debug/deps -L dependency=/Users/user/Workspace/ESP32/esp32-hello-rust/rustlib/target/debug/deps --cap-lints allow` (signal: 6, SIGABRT: process abort signal)
warning: build failed, waiting for other jobs to finish...
error: build failed

Update rustc build with recently releases LLVM 13

Hello,

Could you please issue a new release of the Rust toolchain that built upon recently released Espressif’s LLVM 13?

Thank you.

Add cargo and rust fmt to the toolchain build

Hi,
I’ve been experimenting with my own build of the toolchain for a while now
https://github.com/esp-rs/rust

One of the things I’ve discovered is a unique bug associated with windows when using a linked / custom toolchain such as esp
Typically some tools such as «cargo make» or «rust-analyser» under visual studio code
tend to run cargo multiple times at the same time (similar to running it multithreaded)

If cargo isn’t installed as part of the custom toolchain, then it tends to try and use the cargo native to the host.
But because of the way it does this, it tends to fail under windows when you try to run it more than once at the same time.

rust-lang/rustup#2889

The best workaround I’ve found is to just install cargo into the custom toolchain

# Fixes VSCode Issues with rust-analyser / cargo-make
x.py build --stage 2 cargo

I also tend to add rustfmt for reformatting code

# Add rustfmt for reformatting code
x.py build --stage 2 rustfmt

Would there be any issues in adding these to the workflows script?
I think it would solve a lot of problems associated with rust-analyser and cargo make which are quite useful.

`install-rust-toolchain.sh` bundled with tag 1.57.0.2 installs version 1.57.0.0

I see this has been fixed, but the last release still uses an older version of the install script, so I can’t install the toolchain from a tag on CI, which is not that elegant

Источник

Rust on ESP-IDF «Hello, World» template

Generate the project

Build

Flash

Monitor

Prerequisites

Install Rust (with rustup)

Install Cargo Sub-Commands

Install Rust & Clang toolchains for Espressif SoCs (with espup)

Alternative (for RISC-V Espressif SOCs only): install & use upstream Rust & Clang

(Windows-only) Install Python3

LLVM & Rust

Cross compiling with Rust

ESP Hardware Abstraction Layer

Wiring up ESP-IDF

Making Rust for ESP “out-of-the-box”

Caveats & What’s next?

Thanks to …

Jens Reimann

The compiler

cargo-espflash

idf2svd

The runtime crates

The HAL crates

ESP32

ESP8266

The quickstart

What’s next?

The Rust on ESP Book

Introduction

A note in SoCs support

Status of This Book

Who This Book is For

Additional Resources

esp-rs / rust-build Goto Github PK

rust-build’s Introduction

Table of Contents

Xtensa Installation

Download installer

Download installer in Bash

Download installer in PowerShell

Linux and macOS

Prerequisites

Installation commands

Set up the environment variables

Arguments

Windows x86_64 GNU

Prerequisites x86_64 GNU

Installation commands for PowerShell

Long path limitation

Windows x86_64 MSVC

Prerequisites x86_64 MSVC

Installation commands for PowerShell

Set up the environment variables

Long path limitation

RISC-V Installation

Building projects

Cargo first approach

Idf first approach

Using Containers

Using Dev Containers

rust-build’s People

rust-build’s Issues

Ubuntu 22.04 is using openSSL 3.0 as default

Installing riscv32imc-esp-espidf does not work on Apple M1

Mention in docs that rustup installed through snap has different paths set and creates issues

Shrink LLVM artifact to minimal size

Remove PIP_USER=»yes»

riscv32imc-unknown-none-elf is not recognized by +esp toolchain

SIGABRT: Failed to compile `clap v2.34.0` (on `rust-esp32-std-demo`)

Fix shebang in all scripts

Incomplete installation instructions and script issue

Install extra crate with cargo if no binary package is available

Atomic operations unavaliable on esp8266 chips

Support for ESP-IDF v5.0 CI

Cargo binary for macOS assumes OpenSSL is installed via Homebrew

Use released binary if installing `cargo-generate`

Generate several tags for espressif/idf-rust Dockerhub image

Installer breaks when `-n` is empty

No usable xtensa compiler is installed

Install Rust (with `rustup`)

Install Rust & Clang toolchains for Espressif SoCs (with `espup`)

esp-rs / rust-build
Goto Github
PK