BL652 Default pull up state

RE: BL652 Default pull up state

exigtron — Wed, 13 May 2020 15:24:31 GMT

Ok, I've mailed them too and hopefully get a response. Edvin, thanks for trying to help.

Regards

Shane

RE: BL652 Default pull up state

Edvin — Wed, 13 May 2020 15:18:30 GMT

In that case, it sounds like you need to check with the module producers whether this is possible. I don't know what they are programmed with, and if there is any way to overrule their application. From our perspective, there really isn't much we can do, unfortunately.

BR,

Edvin

RE: BL652 Default pull up state

exigtron — Wed, 13 May 2020 14:38:46 GMT

Hello Edvin, the nAutoRun and SIO_02 are naming conventions referred in the BL652 modules specification. The module comes preloaded with a smartBasic runtime engine that turns on the pull-up on some pins which leads to the problem I mentioned. I was hoping someone here is familiar with the module and how to overcome the problem.

As mentioned, I need to pull the MOSFETs gate low by shorting the jumper. This allows me to erase the nrf52 to set it to the disconnected io state. The problem is it's an added step for each board and is a risk if I forget to remove the jumper.

RE: BL652 Default pull up state

Edvin — Wed, 13 May 2020 13:56:42 GMT

The nRF has a default setting for all the gpios as disconnected input, so the pins aren't pulled up before programming (unless the module that you refer to has a HW pullup, which I doubt that they have).

What is nAutoRun and SIO_02? What pins are those? They are not part of the nRF Spec. Are they referred in the module specification?