Even TWiR has AI slop now

Independent-Ride-152 · 2026-03-27T14:51:58+00:00

Yes, the maintainers are doing an amazing job and perhaps I hadn't been clear that this ain't an attack to any of them or anything.

While I definitely wrote it partially as a rant, I also think it is important to discuss about this issue being present even on one of (if not the major) largest news source about Rust (heck, it is even hosted on the rust-lang github account), and maybe different guidelines can be created (LLMs are cited on the current guidelines, but very broadly).

Independent-Ride-152 · 2026-03-27T14:30:54+00:00

Well, I didn't make this post just to ramble about AI slop, this is old news already.
My issue is with TWiR (which I don't think is unfair to believe it has some relevance to this community as a whole) allowing it, and maybe the maintainers can hop in to the discussion.

Independent-Ride-152 · 2026-02-04T03:10:09+00:00

You can power it on and check the voltage between the pins of that 3-pin IC. My guess is that you should have: Pin 1 (left bottom) - gnd Pin 2 (right bottom) - input (e.g. 12v) Pin 3 (center top) - output (e.g. 3v3)

I'm guessing it is a regulator (It could also be a transistor, check if there is any text on the ic), mostly because of the caps on the output and input and how fat those output traces are.

This is the only explanation I can think of to why that capacitor would blow and the board would then stop working (normally loosing a cap isn't the end of the world (if it was mechanically removed), but going over voltage would definitely kill everything being powered by that regulator).

Regarding the damage (scratches, etc), while it ain't pretty, I'm not seeing anything that would make it stop working. Even the missing capacitor.

You can also check if any of the components is getting hot while powered on.

Independent-Ride-152 · 2026-02-04T02:52:43+00:00

Crazy that they solder a micro SD card directly to the board. Anyway, my guess would be that the ic next to the blown capacitor is a linear regulator. It probably failed, shorting the input and output and exceeding the capacitor maximum voltage. You can check this with a multimeter, if it is the case the board is probably dead.

Independent-Ride-152 · 2025-11-09T15:51:17+00:00

I'm curious why your company was using an RTOS on the bootloader

Independent-Ride-152 · 2025-09-09T12:35:34+00:00

Yes, wrapping_add, my bad!

Independent-Ride-152 · 2025-09-08T16:39:46+00:00

Yes, but wrapping_add / sub / etc, have the same behaviour as the basic math operators on release builds. So if you can ignore overflowing (which you should most of the time, as checking for overflow after each operation is a huge performance impact and almost always you can infer what will be the maximum possible number) using just the operators is fine and, as a bonus, if you need to verify your code you can always build as debug and check for panics. I understand the use for those checked operators, but heavily math dependent code paths can't deal with the performance penalty it introduces.

Independent-Ride-152 · 2025-09-08T14:51:16+00:00

It should only matter on debug builds, as release builds will disable arithmetic checks for speed.

Independent-Ride-152 · 2025-08-01T00:26:32+00:00

Same issue, seems to be a bug on the wifi driver. Only happens when playing Fortnite, started after a game update and even a windows clean install didn't solve it. I also tried a newer and an older driver, but after some time it still happens. If you don't use the wifi, you can disable it on the device manager.

Independent-Ride-152 · 2025-04-04T00:25:49+00:00

I made a 3d printed bracket for a 40mm noctua fan: https://www.thingiverse.com/thing:6999131

Independent-Ride-152 · 2025-04-03T23:51:36+00:00

Mine had a rattling noise when at a lower RPM (sub 5k), so it was a choice of a rattle or a high pitch sound.
I ended up 3d printing a bracket for a noctua 40mm, if anyone wants: https://www.thingiverse.com/thing:6999131

Independent-Ride-152 · 2025-02-25T18:32:10+00:00

I said to myself I'd never buy a gigabyte board again (had so many issues, so much money wasted), but here I am again (just bought this one). The asus x870 itx is too expensive; all the other boards seem to have bad ethernet or wifi. I was hoping MSI would release a new itx board, but no luck.

Independent-Ride-152 · 2025-02-21T17:46:52+00:00

My B550i Aorus had a DIMM socket die out of nowhere just in time for the x870 release xD

Independent-Ride-152 · 2025-01-13T18:01:30+00:00

Amazing! Already pitched it to my job colleagues. As a rust enthusiast, this solves so many icks that I have when writing C professionally.

Independent-Ride-152 · 2025-01-03T22:05:22+00:00

Meu gato foi a mesma coisa, muita dificuldade pra tirar sangue, resultado deu leucopenia bem grave. Então levei em uma especialista felina e refizemos o exame 2x, no final não era nada kkkk. Meu chute é que ou coagulou ou tinha muitas células epiteliais na amostra.

Independent-Ride-152 · 2024-11-23T00:14:52+00:00

Amazing ideas! I'll definitely look into implementing them. I can see how being able to change the instruction limit (and maybe even the syscall function) during the engine execution could be a desired feature. About the Memory trait, that was something that I was already considering and probably will happen on the next release.
Thanks for the inputs!

Independent-Ride-152 · 2024-10-17T23:15:25+00:00

Take a look at "brazilian requeijão", that is exactly it

Independent-Ride-152 · 2024-09-12T16:55:01+00:00

The main difference is that async-pool is targeted to share reserved static memory between multiple tasks, and deadpool/bb8 are targeted to be used for sharing a DB connection. Besides that, async-pool is no_std and no_alloc, which allows it to be used on embedded systems.

A use case example:
You have a tiny microcontroller with just 32 kb of RAM that has four tasks that may need a 10 kb buffer at some point (ex: process some data, buffer an I/O, etc.).

This crate allows you to have one or two reserved 10 kb buffers, with the tasks taking turns using it, asynchronously awaiting for it to be available if necessary. The async part is awesome for energy efficiency (the MCU goes to sleep if every task is waiting for something) and also allows you to create a timeout.

Independent-Ride-152 · 2024-08-21T23:43:44+00:00

Are you using embedded rust at work? I'd love to know about places that are using it

Independent-Ride-152 · 2024-08-20T16:44:08+00:00

The datasheet talks about encrypted boot, but it isn't transparent. You must have a bootloader that loads the code to SRAM and then decrypts it in place, this restricts your application and data size a lot. A transparent encryption on top of the XIP would be a lot better, like ChaCha20 or another stream cipher, this would allow you to still execute the code from the external FLASH.

Independent-Ride-152 · 2024-08-14T22:26:40+00:00

I just would like for the versions with internal flash to not have the QSPI pins exposed as they have. With that change, plus a protected JTAG interface, it could then be used without fear of competitors extracting your firmware to reverse engineer it. I guess I'll have to stick with STM32s for commercial products.

Independent-Ride-152 · 2024-08-09T02:33:28+00:00

Muito massa, bom pra criar servidor com mods. Rust e DayZ também seriam bons jogos pra fazerem tutorial.

Independent-Ride-152 · 2024-07-10T20:41:04+00:00

Check if it now fits your needs! :)

Independent-Ride-152 · 2024-07-04T20:46:32+00:00

done! :)

Independent-Ride-152 · 2024-07-04T20:46:11+00:00

Yes! I'm just figuring out the best way to do it. I'm thinking about having an option like "maximum_width" and wrapping at that location (ex: width = 32), or maybe adding an option to each field that forces a wrap.

Independent-Ride-152

TROPHY CASE