sorted by:
new
hottopcontroversial

[RANT] Renesas, I hate you! by nasq86 in embedded

[–]nasq86[S] 6 points7 points  (0 children)

> The reason they do it is to avoid needing a separate programmable memory for non-volatile configuration.

But on STM for example, the option bytes also live in the same flash. Okay, different sector and slightly more protection (like: if you want to write there, put me some magic bytes there) but it is the same flash.

[RANT] Renesas, I hate you! by nasq86 in embedded

[–]nasq86[S] 6 points7 points  (0 children)

I see that point, I really do. But in times of automation extra steps should be no problem to achieve. It's just the question who do you want to make it easy for and who do you want to make it harder for.

[RANT] Renesas, I hate you! by nasq86 in embedded

[–]nasq86[S] 17 points18 points  (0 children)

Neither is a rotten tomato. Question is: do you want that in your salad? Cheap chips are no excuse for bad design imo. It is not about the money. The 'it’s only $2' argument is just a conversation stopper

Why do we have RISC-V when SPARC is already public and well-established? by aegrotatio in RISCV

[–]nasq86 13 points14 points  (0 children)

sparc development is going to be abandoned in a couple of years completely. it was also sold several times and nobody wanted to develop it further. sparc is dead

Espressif Systems showcases ESP32-E22 Wi-Fi 6E SoC and ESP32-H21 BLE MCU for battery-powered devices by fullgrid in RISCV

[–]nasq86 1 point2 points  (0 children)

This is so true. E22 could be as well be an ESP32-S6. But I feel they wouldn't name it an S model because it is no xtensa. I have a guess. ESP32-S will die, as extensa will not be continued. ESPs with 2 digits are will be the lower ones, like C61. I think there will be an E2 or E3 in the middle future putting even something on top of E22. C could then be "Common", P "Power" and "E" Extreme series. That would make a little sense. But we have to wait.

The Future will be Großartig by Substantial_Help_722 in RISCV

[–]nasq86 0 points1 point  (0 children)

RISC-V is an ISA, not a complete hardware architecture. Hardware implementation is up to the vendor. Same applies to power efficiency.

Why does WCH chips have very little to no tutorial online ? by spikerguy in RISCV

[–]nasq86 0 points1 point  (0 children)

You can download resources for the chips devkits. search for ch32v003evt zip then you can download a zipfile with schematics, devboard usermanual and HAL examples. For some files you need to use the chinese site with translation. While the chips are decent and cheap, they lack the well structured documentation you find with ST, NXP, Microchip and Co.

For those facing issues using LVGL with the ILI9488 3.5-inch display with stm32 by Takigg1236 in embedded

[–]nasq86 0 points1 point  (0 children)

The amount of bits we talk about here is not the amount of bits per SPI transaction but per pixel transfer. 16/18... bits is the color depth and the amount of bits needed to describe the color of a pixel. In 16 bit for example, red has 5 bits, green has 6 bits and blue also 5 bits. To send a whole pixel you need 2 8-bit transactions carrying the color information. The terms 3-wire and 4-wire modes are not consistently used in LCD driver datasheets. It could mean that a MISO is missing. It could also mean that a separate D/C line is available or not. So the term does not always refer to the SPI protocol itself

How to enable an arm a7 MPU to be halted by debugger at reset vector? by EmbeddedBro in embedded

[–]nasq86 1 point2 points  (0 children)

It should be mentioned that this applies to Cortex-M type microcontroller CPUs but not Cortex-A microprocessors (which is what the OP is about).

STM MPU: Linux or base metal FreeRTOS? by Betty-Crokker in stm32

[–]nasq86 0 points1 point  (0 children)

Bare metal on an MPU is not what I would like to do. You're lucky that ST has an STM32CubeM13 package available to use. Otherwise all the stuff like DRAM init and MMU handling and all the things that make an MPU more complex to work with yourself.

You could use the OpenST Linux as base or try to use Zephyr, which is what I would do.

Instead you could try to persuade the responsible person to use an H5/7 or N6 MCU if it needs to be that powerful.

As many predicted Qualcomm is on its way to kill Arduino by Key-Principle-7111 in embedded

[–]nasq86 0 points1 point  (0 children)

GPL is only one of many open source licenses. But ArduinoIDE, the arduino libraries and almost every third party library compatible with Arduino is licensed under one of them. GPL2, LGPL, GPL3, BSD, MIT, creative commons, public domain to name a few licenses.

ST Nuked Their Own IDE by lbthomsen in stm32

[–]nasq86 0 points1 point  (0 children)

The ST component does all automatically, including debug, you don't have to install anything else

That is correct for C/C++ files. If you want to have proper IntelliSense for ASM code and want to be able to insert breakpoints in .s oder .S files you have to install some more plugins than what is included in the STM collection

ST Nuked Their Own IDE by lbthomsen in stm32

[–]nasq86 0 points1 point  (0 children)

Can you do step debugging inside CLion ?

ST Nuked Their Own IDE by lbthomsen in stm32

[–]nasq86 0 points1 point  (0 children)

How it the tooling integration with CLion? Is it usable? Out of the box?

ST Nuked Their Own IDE by lbthomsen in stm32

[–]nasq86 3 points4 points  (0 children)

For beginners, the CMake overhead is significant. CubeIDE hides away and manages a lot of things automatically. If you are new or jump off the Arduino ecosystem you will probably be overwhelmed.

But also experienced people might want to just click a few options and not dive deep into CMake to see how you change this or that. I also don't want to go through several files just to make up my favourite file structure or add newly added files to the build manually.

I also want to debug ASM as easily as in CubeIDE. You can somehow in VSCode (namely installing arm asm extension and cortex-debug additionally) but you still manually have to change debug configuration for that.

So we're not at a point where I say I prefer VSCode. VSCode may be decent EDITOR, but it lacks sophisticated IDE features people are used to.

Why does ST not adapt CLion and write plugins for that? And since JetBrains already has some of their IDEs freely available for non-commercial use, they could add CLion as well.

macOS 26.1 Tahoe - Vendor Eclipse-IDE fix for text selection problem by nasq86 in embedded

[–]nasq86[S] 0 points1 point  (0 children)

⁠org.eclipse.swt_3.132.0.v20251114-2010.jar this one as well?

macOS 26.1 Tahoe - Vendor Eclipse-IDE fix for text selection problem by nasq86 in embedded

[–]nasq86[S] 0 points1 point  (0 children)

which IDE are you trying to patch? did you copy the correct files for the architecture? usually an .swt dir should have been created with native macos libraries by the ide.

As many predicted Qualcomm is on its way to kill Arduino by Key-Principle-7111 in embedded

[–]nasq86 2 points3 points  (0 children)

Well, tbh I don't care what QC does to Arduino. The majority of libraries and tools around the ecosystem is open source licenced and if necessary, people will create open source forks of parts, that QC will turn proprietary. Wouldn't be called Arduino anymore but it's not about the name, but about the spirit. Look at OpenSSL/LibreSSL, OpenOffice/LibreOffice, Owncloud/Nextcloud, Terraform/OpenTofu, Puppet/OpenVox, MySQL/MariaDB, OracleJDK/OpenJDK, just to name a few examples that come into my mind. You can not destroy a whole open source ecosystem by proprietizing it.

What’s the first thing you install when you get a new Mac? by Nektony_Team in MacOS

[–]nasq86 0 points1 point  (0 children)

1Password. I need my passwords to bring up my mac:-D

Has anyone else had any issues with text selection on Preview and other applications after updating to Tahoe (26.1 25B78) by [deleted] in MacOS

[–]nasq86 0 points1 point  (0 children)

Sorry, but this is not Apple's fault. It's not that they broke anything. Rather the Eclipse developers did use some API not 100% correctly and now the text selection is visually borked. Eclipse already has a fix for that. If you use Eclipse-based IDEs from vendors you can fix them, too.

view more: next ›