I think adafruit core is nice, and they added freertos which is a nice touch too. So, in case, I can easily reuse some modules I wrote for esp32 projects (which is freertos based too, out of he box)

Good to know, it's not perfect, both cores, nrf5 adafruit or arduino-mbed, unfortunately miss some sdk files..

I like Adafruit core so far, but Segger IDE with full sdk support is very convenient, because spending time in arduino cores linking missing libs etc is such waste of time, vs coding fun features..

@neverdie
afaik BMP officially targets ARM mcus, whereas ESP32 is not ARM, it's Tensilica.

@NeverDie
I don't remember exctly, but voltage requirements for mcu only might be the same (approx). On modules, it can differ, depending on external spiflash&ram voltage requirements.

I thought you were talking about the esp32-s2, announced a few months ago, which has usb and few more IOs for example but it's single core.
the simple S version is maybe used as coprocessor, like on particle boards, if I'm not wrong

@NeverDie
so you haven't played with it yet? then you're missing something

well depends what you need to do, sure, but actually when I need to use a mcu, at work too, I almost always use it. I don't use sleep mode.

that's a while I've used 8bits mcu.. because for ESP32 price:

• dual core,
• you can do all sort of "realtime" stuff, and monitor through wifi,
• for example run complex communication on a core while running another complex main app on the other core, thx to rtos too
• well supported in arduino platfom,
• embed servers, webapps..(or just make an api with a native app for ui and uses spiflash for others things)
• widely available module with multiple options (spiflash ,ram etc) for cheap

I don't know a mcu which meets all these ticks

I've not tried the ESP32S version so far, because I've many non-S here, and if I remember the S is not dualcore, still it adds a few things.

I've almost all what I need with ESP32, only missing a few periph and pins. but there are always workarounds.
And, it's better to choose the solution which fits best to the usecase of course. I'm not saying I would choose it for all my projects.

@nagelc
exactly, you're right! Better memory than me I remember now, I had to hack w5100 lib for spi transactions to make it working on same bus. So I don't know if it has been fixed.. I hope so.

@Sergio-Rius
unfortunaly I can't help with your enc28j60 issue. and I'm not sure to have one for testing this.

A while back, we checked w5100 module + arduino 328p. Eth module and radio were working on same hw spi bus but in docs it uses softspi, I don't remember why, perhaps for having a dedicated spibus for ethernet..
I understand this is not very convenient to find the infos, when always more hw is supported.

Just a note, as you are using a Nano for your tests, RFMs modules are not 5v tolerant in theory, even if they seem to handle it, datasheet says 3.9v for max. good to know. but maybe you're already using a level converter.

@monte
it's not standing against diy'ing etc..really you didn't understand my point, it's just about user friendly and easily repetable getting started for MySensors nrf5 newcomers, for simply flashing their sketch.. even if a diy BMP is certainly a good probe too. and a genuine BMP is more expensive than a jlink mini. Compare both a jlink vs a blank diy probe, and with a stopwatch, you'll see which method is faster and easier for a noob..

But ok, I won't insist anymore, if you prefer to get me wrong, really don't mind.. I should better let user with not much xp manage all alone so no debate, as this just makes me less active, see you next year

Just don't forget future newcomers will read your advices. In the meantime, we'll try to update docs for MySensors nrf5.

Have fun with your probe

@monte said in nRF5 action!:

@scalz well, that's nice that you know what you want and can get it, but that doesn't mean that's suitable for everybody else. That's good to have a choice, but when you need it done, you better find a way to get it done easier and faster.

Why so much impatience So many things to tinker.. I mean you can get a jlink in 2days if you need it. I ordered mine while I was waiting for stuff coming from China..and in my case, there is no close-door store for geeks.
Do you mean you would suggest a nrf5 newcomer to diy a BMP for mcu flashing??

When I got my jlink, I didn't have to flash it to make it working.. I just had to donwload win drivers, install them, and voilà.
Which proprietary sw do you think you need to learn?? I don't use any special sw for flashing..just regular IDEs like arduino/vs studio, or more advanced like Segger (free) or Keil. For all these IDEs, I just click on a button to upload fw, simple. There is nordic windows apps, or nrfjlink in CLI too.

I know the power of oss and its flaws, same for commercial, in practice it's not rare to see communities sitting/waiting for updates (not hard to find examples on github), whereas money makes commercial products live.
No need to debate on this, it's useless debate I think
The reality is different here, I think you'll find more subscriptions-free resources on internet about Jlink than BMP, and for a reason I agree that you'll find lot of howtos save a few bucks by diy-ing and flashing a BMP..
everyone acts in one's own interest
Just to sum up my thought, I think for a newcomer it's easier to get started with a Jlink vs diy probe that you need to flash with what, a probe ??

Below is a screenshot of a running nrf5 test, stability test.. but for example you can see, I don't use any additional uart for debug printing, and fw is just uploaded by a click in IDE.

"BMP is open-source, meaning that you can look inside it if you need or want to"

"The GDB server is implemented on the probe itself, this means we do not use some proprietary protocol to talk to your debugger software"

sounds so useful when you simply want to upload fw and debug
open-source does not mean better quality than proprietary imho, it can be a burden too. I prefer mature product for working.

is BMP compatible/integrated with as many IDE as a proprietary probe?
If for instance someday you want to use it with Segger IDE+nordic sdk, is it compatible? I don't think so.
I "compared" probes recently and decided to stick to jlink. The second probe in my list is cmsis-dap/daplink, looks nice too, but don't need it (at least, not so far)

I use many different toolchains and CLI too. So when there is a tool that just needs download and exec to install driver, autoupdates etc, without spending life in CLI, I don't hesitate.

struggling or working..

@Sergio-Rius
I can't help you with blackmagic probe unfortunately.
Just personal opinion, I prefer Segger probe.
For example, Segger EDU mini is cheap. for the price don't bother with clones..

• very affordable
• compatible with a lot of IDEs, and when you use it with Segger IDE then you get best integration
• segger provides lot of tools for debugging for free
• easy updates and drivers install

The only cons to a jlink probe could be no additional uart, but I don't need uart for debug&prints (segger ozone and rtt tools), and nor uploading sketch.

Or a nrf5dk board is a nice alternative too, a little bit more expensive than EDU Mini but you get jlink+devboard+ later you could hook a power profiler kit on it
Still a jlink mini at hand is quite useful.

Like I said just personal, I'm sure BMP is nice too, I guess you'll get it working before you can get a jlink