←back to thread

129 points hasheddan | 1 comments | | HN request time: 0.322s | source
Show context
SOLAR_FIELDS ◴[] No.44367397[source]
Nordic makes some good products. When I was doing hardware design for a product that uses a battery my options for power profiling were either not to do it or spend some eye watering amount of money. Then I discovered Nordic makes the PPKII, a cost effective, highly accurate profiler with quite good software. I detect good things in store for the company just based on the quality of stuff they have been putting out.
replies(7): >>44367526 #>>44367601 #>>44367674 #>>44367996 #>>44368169 #>>44371842 #>>44372816 #
monegator ◴[] No.44367601[source]
> Nordic makes some good products

and godawful software. the SDK for their NRF52/3/4 is pure madness, i haven't even managed to set up the toolchain, documentation always out of date. They used to have another toolchain for the older parts, but good luck setting it up now.

replies(4): >>44367823 #>>44368255 #>>44368654 #>>44369851 #
mystified5016 ◴[] No.44369851[source]
I spent so much time trying to get the SDK working for NRF52 that I genuinely just gave up and redesigned our whole product to use an ESP32 instead of the NRF plus other uC.

I think that is genuinely the reason espressif is eating everyone's lunch. All the old players in the IC business have such inexcusably bad SDKs that the acceptably designed and documented ESP-IDF framework just makes the most sense to use. Why would I spend six weeks fighting with Nordic SDKs with their weird system-wide installation when ESP-IDF can be set up in five minutes isolated to your user directory?

Seriously, it takes longer to find the correct Nordic SDK installer than it does to git clone, idf.py install, ./export.sh

And Nordic's weird documentation web portal is just egregiously bad. Espressif puts it in a static HTML page with a selector for the framework version. It's simple, elegant, and fast.

I did like using the NRF52 once it was finally behaving, but the ESP is just so easy.

replies(1): >>44371076 #
vbezhenar ◴[] No.44371076[source]
I've found old SDK actually not that bad. Documentation is not great, but sources are available and it's just mostly C code with some hairy macros, but it's manageable. After few weeks I became quite proficient. I don't like their suggested approach "copy&paste example you like and tinker it", I never do that, so I had to untangle their Makefiles, I had to research their defines (app_config.h, what's a monstrosity), I had to write my own linker scripts, but in the end I have my application under control and it's all standard gcc toolchain, no fancy stuff.
replies(1): >>44371979 #
1. Avamander ◴[] No.44371979[source]
> I don't like their suggested approach "copy&paste example you like and tinker it", I never do that, so I had to untangle their Makefiles, I had to research their defines (app_config.h, what's a monstrosity), I had to write my own linker scripts, but in the end I have my application under control and it's all standard gcc toolchain, no fancy stuff.

Sounds very similar to ST.