MicroPython Forum (Archive)

It’s actually a bytes , not a bytearray (former is immutable, latter is mutable). Try type(myHash) and read https://docs.python.org/3/library/stdtypes.html to learn about Python’s built-in types. You didn’t specify what your resulting string should be, but one way of converting your hexHash (a byte...

But the nus console which is using nodejs noble just sits there waiting forever for a connection, it seems that this may be related to noble incompatibility with osx mojave which I am running. FWIW, I also couldn't get that to work either. However, I decided not to dwell on it, since the WebBluetoo...

The trouble is, >>> myHash b'\x93\x1d\x93HP\xf6,.2\x856\x0e\t\x80\xed\xd9\xaf\rc\xff\xbb9\xf6~\xa8\xca\xea\x9ca\xf2\xbd\xd4' is not a string, as confirmed by: >>> isinstance(myHash, str) False but it doesn't seem to behave like a number either: >>> print("0x{:02X}".format(myHash)) Traceback (most re...

The problem is whilst I am working on this, as I am breaking new ground with an untested board and a non-standard programer, I am not sure if these problems are related to my non-standard programming method (openocd) or are inherent in the build for this device. Here's 3 problems I have, do you hav...

I have my first pass on nRF52840 OTA updates (using Nordic's proprietary radio mode) now working with micropython. So, proof of concept works. :D I feel I should improve the code a bit before posting it though. For instance, I should probably add a hash function like MD5 or SHA256 to ensure the enti...

BTW, if you haven't already, you may want to look into Nordic's nRF52840-DONGLE. At $10, it's only slightly more than your HolyIOT. Also, it passed FCC (which I don't know if that matters, since you are in Singapore). On the other hand, the HolyIOT has more pins exposed, so there is that in its favor.

Try it again but with SD=140, as per your other thread (viewtopic.php?f=12&t=5348&start=20), since you are using an nRF52840. Sounds as though you are very close to getting it. Then you can join the club.

Nice work.

Yeah, 9 and 10 can be made to work by disabling NFC on them, but they are slightly crippled (relative to other pins) even if you do, so I think you're right: it's best to avoid them if you can.

I think I may see your gotcha. You are using an nRF52840, not an nRF52832. Thus, if I'm inferring correctly, you should set SD=140, not SD=132 during your make. Likewise, any flag changes in the bluetooth config file should be made in that section so that they will trigger when you set SD=140.

There's a bona fide Segger built into the nRF52840-DK, so the DK is a pretty good value when you consider that a standalone Segger costs much much more. Like I mentioned, the DK's Segger can be used for programming external nRF52840 modules like your HolyIOT. It's not limited to programming only the...