Thingy91 skipped orange breathing during setup

[cachro2]

Hi,

I received a Thingy91 and am unable to commission it to nrFCloud.

The Thingy91 skipped orange breathing as mentioned in the manual here (step 4). It went directly to cyan breathing which is weird since I believe it thinks it is associated to the cloud..

It was purchased brand new a few days ago and SIM card is activated through the nRF Cloud portal.

Before I go ahead and update modem firmware and the such, any thoughts?

Thanks,

Robert

[Heidi]

Hi!

The manual you linked to is an older version with incorrect information. The newest Thingy:91 Getting Started Guide v1.3 states that the cyan color means that the device is connecting to nRF Cloud. So that can take a few minutes and then when it starts to blink yellow, your device is connected and is awaiting user association. 

When it is connected to nRF Cloud and sending data, it will flash a dark blue.

However, it is important to update both the application firmware and the modem firmware on the nRF9160 SiP before beginning. You can take a look at our Thingy:91 Getting Started video for easy information on how to do this. 

Best regards,

Heidi

[cachro2]

Thank you Heidi, we are up and running!!

One additional question:

I scanned the manual and didn't find a concrete answer. Is there a spare UART peripheral exposed and accessible on the Thingy91? I ask because our prototype asset tracking units need to pull data from an external microprocessor to function properly.

Thank you,

Robert

[Heidi]

Hi!

No, it does not look like there are any spare UART peripherals. This isn't very well documented but if you take a look at the code you can see that UART0, UART1, I2C2 and SPI3 are all enabled. Since UART2 and UART 3 share an ID with those last two, they cannot be used simultaneously. 

You can however access either UART2 or UART3 by disabling the peripheral with the corresponding ID, or switch between the two peripherals, as described here.

Best regards,

Heidi

[cachro2]

Heidi,

Thank you again!

I took a look at the Thingy91 schematic and it seems like the I2C2 reads/writes to environmental sensors + EEPROM, etc. and the SPI3 maps to the two accelerometers. I cannot tell what the two UARTs (UART0 and UART1) are mapped to by looking at the schematic. Likely a connection between the nrf52840 and nrf9160 is one of them and perhaps GPS another?

Can you please point to where these peripherals are defined in the asset_tracker code? I am having difficulty locating any mention of UART0, UART1, I2C2, etc.

Best,

Robert

[Heidi]

Yes, I2C2 for sensors, SPI3 for accelerometers. UART0 is for communication between the nRF9160 and the nRF52840. And UART1 is to be able to get modem tracing from the modem on the nRF9160 SiP. 

This file (src/env_sensors/bsec.c) is where I2C is used. This line is the initialization of the I2C2 peripheral. It is also used in the temperature sensor, see the BME680 driver.

As for SPI3, the Thingy.91 uses the accelerometer ADXL362. If you take a look at the driver for this sensor, you can see it uses SPI. 

As for the UART peripherals, I don't think there's any specific mention of them in the application This BSD Lib config, CONFIG_BSD_LIBRARY_TRACE_ENABLED enables UART1.

And if you dig around in the logging module (see log_backend_uart.c), you can see that it uses UART_0 by default.

So, if you enable logging over RTT instead of UART, UART_0 is free and I believe you then get one available UART peripheral that you can use for something else.