MicroPython Forum

I wonder if there is some work being done on the NFC support for the nRF52. Other users seems to have asked the same questions so I thought I open a separate topic.

I'm willing to join or help on this issue but need some pointers within the nRF SDK on where / how a possible integration could be done.

@c45713 The the experiements it was basically found that FATFS on internal flash used a bit to much in overhead, at least for nrf51 and in practice also for nrf52. The findings were that 50 pages had to be reserved in order to even make the FATFS structures, then the file storage came on top of this...

there is the mboot bootloader module in the stm32 port, from damien https://github.com/micropython/micropython/tree/master/ports/stm32/mboot basically implements DFU over USB and I2C, with support to write external SPI chips. I think he might use this one in his upcoming new pyboard devices, thats w...

What I‘ve figured is that the nRF port has the micro:bit FS enabled as default which only supports flat file hirarchies (no directories). Also, I see that os.listdir(‚.‘) reports an error about an argument given... both of which might relate to the problems you see. There is a small section in the r...

It doesn't rely upon nor use softdevice.

What I meant to ask was that *if* the softdevice is included (in case you want to use standard Btle functionality too), doesn‘t it interfere with your code (because you are directly manipulating hw registers)?

I‘m wondering how the softdevice coorporate with this... do you include it in your flash output at all?

And just a small thing: please rephrase the title of this thread so it reads correctly („nRF52“) - makes it a lot easier to search.

that is great, thanks!

Do you mind sharing this as a git gist or even as a git repo so that scanning through the code and making comments is easier?

pythoncoder wrote: ↑

Sat Oct 06, 2018 5:43 am

Out of interest how quickly does it boot?

he told me around 4sec...

viewtopic.php?f=12&t=5039&p=28855#p28907

scanning through the datasheet.. . that is a standard memory mapped i2c device. so you should be fine by using any of the i2c.memread/memwrite functions. start ln the repl, do a scan first. then try to read the device id. once that works, you should have no problems initiating the measurement functi...

+1 from me too.
and +2 for examples and hints on using uctypes...