Thingy 53 + nRF7002eb supply anomaly

[aamoros@INVOLI]

Hello,

I am evaluating the Thingy 53 + nRF7002 EB for Wifi and Bluetooth scanning. 

But depending on which power source I plug the devkit, the wifi interface doesn't set up. For instance, on the same PC, one USB port can deliver enough power, and another one (with the same hardware characteristics) does not.

I assume it's related to the nPM1100 power management IC, because USB port detection can limit VBUS current on the board. Nevertheless, I tried to set the GPIO ISET high to have a limit of 500mA instead of 100mA but nothing changed.

I run on  the sample app called wifi scan the board and connect it with a 3.0 USB cable.

Please, can anyone give a clue on this issue ?

[Amanda Hsieh]

Hi, 

It needs to build for the nRF7002 EB with Thingy:53 and program the image to make nRF7002 EB get power and work, for example:

west build -b thingy53_nrf5340_cpuapp -- -DSHIELD=nrf7002eb

See Getting started with nRF7002 EB doc.

Regards,
Amanda H.

[aamoros@INVOLI]

Thanks for replying.

I have done this in the build configuration tool of nRF connect sdk extension for VS code, following this instruction:

To build with the nRF Connect for VS Code extension, specify -DSHIELD=nrf7002eb in the Extra Cmake arguments field.

Would it change something ?

[Amanda Hsieh]

It would include the overlay for nRF7002 EB. Check out the build log. 

[aamoros@INVOLI]

Thanks for this information.

But I don't think it's the issue because the same firmware can work depending on the USB supply. For example, it works when I plug the thingy 53 in my personal laptop but not in my professional laptop...

[Amanda Hsieh]

aamoros@INVOLI said:

For example, it works when I plug the thingy 53 in my personal laptop but not in my professional laptop...

Do you install the related firmware on another laptop such nRF Command link tool? When installing JLink on a completely new system, the default behavior is not to install the USB driver(s)! You should enable it.