Thingy 91 won't connect to network

[GJSea]

Hi,

I have simple test firmware that simply connects to the network and goes into PSM sleep, it works perfectly well on the nRF9160DK but the Thingy 91 is refusing to connect and either doesn't get any events from the lte_lc_connect_async handler, or does get a LTE_LC_NW_REG_SEARCHING event, but doesn't proceed to ROAMING/HOME. I'm swapping the same SIM between the two. Is there anything specific that needs to be done to get the antenna tuning set correctly for the pair of QM12038's for the US AT&T network?

Thanks!

[Martin Lesund]

Hi GJsea,

The QM12038 switches are controlled using the MAGPIO pins on the nRF160. These need to be configured via AT command %XMAGPIO. Do also make sure that when you are building the project you are building it for the "thingy91_nrf9160ns" board.

Also please a look at the hardware files for the Thingy:91 and this application note published by Fractus for more information about the design for multiple matching networks.

Best regards,
martin L.

[GJSea]

Thanks Martin for the reply, I thought the 9160 automatically controlled the MAGPIO pins automatically, if I call If I use the thingy91_board_init(...) code then do you think this will resolve the issue? What are the differences in the board definition files between the DK and the Thingy so I can coerce my firmware to correctly drive the Thingy? My ultimate goal was to performance test the Fractus antenna + its matching circuitry so as to incorporate it into a new design. 

Thanks!

[Martin Lesund]

Hi GJsea,
Did you use the same exact .hex file on the DK and the Thingy:91?

When you build the project for the Thingy:91 (thingy91_nrf9160ns) it will automatically select the MAGPIO settings that you see in the board files I linked to in last post. So I would recommend that you build the same project for the Thingy board. (calling the thingy91_board_init() could work as well, but would in my opinion I would recommend building for the correct board).

• Thingy:91 Board files
• nRF9160DK Board files 
  
  

For example when you build the Asset Tracker application for Thingy:91 it will automatically select the Thingy:91 board files as linked to, but also select the configuration files in the project to utilize the on board sensors instead of the simulated ones that are used when building for the nRF9160DK.

How to configure the MAGPIO for external devices are also mentioned in the White Paper: "nRF9160 Hardware Verification Guidelines"

Best regard,
Martin L.

[GJSea]

Hi Martin,

By pulling in thingy91_magpio_configure() and related #defines from board_nonsecure.c into my main application, I can confirm everything now connects perfectly well. 

Thanks!