LoPy with 3.3V direct powering fails to start.

[jmarcelino]

@robert-hh
Yes I noticed that when I pasted the text here, already let them know :-) Thanks.

[cocoa]

@jmarcelino @robert-hh @ssmith

Thanks for help to solve this issue.

[jcaron]

@jmarcelino @robert-hh

Isn't this the opposite of what what stated here:
https://forum.pycom.io/topic/1022/root-causes-of-high-deep-sleep-current

Workaround:
Power the board via the 3V3 pin using a stable 3V3 supply that is able to deliver at least 400mA. This lowers the deep-sleep current to around 2.5mA.

?

Also, it's unclear to me what the setup on the Pysense/Pytrack actually is? Is the Pysense/Pytrack sending power to the module via 5V, and then receiving 3V3 back from it (which I suppose only goes to the 3V3_Pymodule pin)? Someone I had thought the module was powered by the Pysense/Pytrack via the 3V3 pin, but that's probably incorrect.

[jmarcelino]

@jcaron

Isn't this the opposite of what what stated here:

Not completely the opposite, it's still more efficient to use a regulated 3.3V supply (low voltage forces the onboard regulator into bypass ECO mode)

But it needs to be updated to reflect that 3.3V should be applied to the 5V/VIN pin.

Is the Pysense/Pytrack sending power to the module via 5V

Yes, all the various shields implementing deep sleep control the *py board's 5V rail