I-NUCLEO-LRWAN1

[Tesla DeLorean]

Posted on September 15, 2017 at 18:55

USI LoRa module

http://www.st.com/en/evaluation-tools/i-nucleo-lrwan1.html

Anyone else ported I-CUBE-LRWAN to the USI Module?

What's your experience with the RSSI level vs other SX1272/SX1276 solutions?

Note: this post was migrated and contained many threaded conversations, some content may be missing.

[Andrew Neil]

Posted on October 27, 2017 at 17:08

To me, this is a huge red warning light with bells & sirens about using the USI product!

Surely, the whole point of creating this board is to encourage people to use their module?

So, if the level of support before they've made the sale - ie, before you're committed - is so poor,  what's it going to be like once they've got you on the hook with nowhere else to go??

Did nobody at ST check that there was adequate documentation before allowing this to be featured on their website and with their branding?

[Andrew Neil]

Posted on October 27, 2017 at 17:10

Thomas Roell wrote:

what sensor is connected how to the USB module

Err - there isn't any USB on it?

[Thomas Roell]

Posted on October 27, 2017 at 17:19

s/USB/USI/g 😉

I suppose the sensors are somehow connected to the Arduino headers (should be in the I-CUBE-LRWAN package from ST). But what would be more interesting is whether the sensors are connected to the USI module or not.

It's just ultra-frustrating to have this sitting around here and not being able to do ANYTHING with it. How am I supposed to measure power consumption if I don't know how to disable the sensors ? Or program some GPIO triggers from the USI module to trigger the measurement ...

The PCB looks well designed, so I'd suppose they thought about all of this. Just please send me the document with the jumpers, the solder bridges and the schematics. It's not like there is likely to be any top secret in the schematics.

The USI module itself is mostly reasonably documented (fccid.gov has the module docs as usable as well). 

[Tesla DeLorean]

Posted on October 27, 2017 at 17:26

Accelerometer + Magnetometer Sensor

LSM303AGRSB1/SB2 connect SCL/SDAI2C Address 0x32 AccI2C Address 0x3C MagJP1 VDDJP12 LSM303AGR_INT PB1LSM303AGR_DRDY PA7Relative Humidity and Temperature SensorHTS221SB9/SB10 Connect SDA/SCLI2C Address 0xBEJP3 CS

Pressure Sensor

LPS22HBSB11/SB12 SCL/SDASB13/SB14 SDO VDD/VSSI2C Address 0xBAJP4 VDDLPS22H_INT1 - LPTIM1_IN1 PB5SB19 I2C SDA ARDUINO HEADER (D15) PB7SB20 I2C SCL ARDUINO HEADER (D14) PB6SB32 COMP1_INP ARDUINO HEADER (D11) PA1SB33 COMP1_OUT ARDUINO HEADER (D10) PA11SB34 RCC_MCO ARDUINO HEADER (D8) PA8SB29 SYS_WKUP1 ARDUINO HEADER (D7) PA0SB30 LPUART_TX ARDUINO HEADER (D1) PB10SB31 LPUART_RX ARDUINO HEADER (D0) PB11SB28 LPS22H_INT1 ARDUINO HEADER (D5) PB5 (LPTIM1_IN1)SB27 LPS22H_INT1 ARDUINO HEADER (D3)SB26 HTS22_DRDY ARDUINO HEADER (D4) PB2 (LPTIM1_OUT)SB25 HTS22_DRDY ARDUINO HEADER (D6)

SB35 ADC_IN8 ARDUINO HEADER (A1) PB0

SB24 LSM303AGR_INT ARDUINO HEADER (A2) PB1 (ADC_IN9)SB23 LSM303AGR_INT ARDUINO HEADER (A4)SB22 LSM303AGR_DRDY ARDUINO HEADER (A3) PA7 (ADC_IN7)SB21 LSM303AGR_DRDY ARDUINO HEADER (A5)

SB36 VDD_FRS

SB37 VDD_3V3

R15 PB5/LPTIM1_INT (LPS22H_INT1)

R16 PB2/LPTIM1_OUT (HTS221_DRDY)R17 PA7/ADC_IN7 (LSM303AGR_DRDY)R18 PB1/ADC_IN9 (LSM303AGR_INT)R19 PB6/I2C1_SCLR20 PB7/I2C1_SDAR69 BOOT GND

JP13 1=RF_SW_CTRL1, 2=RF_SW_CTRL2

 LD1 GREEN LED ARDUINO HEADER (A0) 

[Tesla DeLorean]

Posted on October 27, 2017 at 17:32

It is a USI board, and they have decide be closed source, the AT Modem outputs some assorted Chinglish messages.

[Thomas Roell]

Posted on October 27, 2017 at 18:18

Thanx Clive ... Did you get the docs or did the dirty work yourself ?

So if I see this correct, you'd want to short R15/R16/R17/R18/R19/R20 to have the sensors connected to the USI module.

If you also short the other relevant solder bridges you can get:

PA0 (SB29, default on)

PA1 (SB32, default on)

PA7 (SB22, default off)

PA8 (SB34, default on)

PA11 (SB33, default on)

PB0 (SB35, default off)

PB1 (SB24, default off)

PB5 (SB28, default on)

PB6 (SB20, default on)

PB7 (SB19, default on)

PB10 (SB30, default on)

PB11 (SB31, default on)

Down to SB22/SB24/SB35 ...

That leaves PA0/PA1/PA8/PA11/PB0/PB10/PB11 to play with ...

Not sure about your definition of JP12. I see 3 pins on that. Looks like it connects something else CS to GND/VDD to select the I2C address for LSM303AGR ?

Now internally PA4 is connected somehow to measure battery voltage ? Is this connected somehow to JP7 ? Or is JP7 just a I2C header ?

There is S1 (the switch) ... Any idea there ? NRST ? Or BOOT via R69 ?

Is JP8 by chance the SPI port ? 

Is JP9 by chance DIO0/DIO1/DIO2/DIO3/DIO4/DIO5/RESET (reset for SX1272 ?)

So only JP2, JP14, JP15 😉 Bet JP2 is connecting 3V3 from the header. With that logic JP14 connects VIN (for what ? PA4 ?) and JP15 is for GND. 

[Tesla DeLorean]

Posted on October 27, 2017 at 19:04

I created this quick digest from the schematic this morning. The earlier pin lists were done from the data sheets of the module and the STM32 datasheet. I had done that to see how easy the port would be, but the Murata solution had a better L0 part, and SX1276, so I focused on that.

I have since soldered an SWD header on the USI board and replaced the firmware with a port of the LRWAN tree.

By default I think most things are hooked up, the Arduino pin options tend to select one or the other.

>>Is JP8 by chance the SPI port ? 

Yes

>>Is JP9 by chance DIO0/DIO1/DIO2/DIO3/DIO4/DIO5/RESET (reset for SX1272 ?)

Yes

PM me with an email address for the schematic.

[Tesla DeLorean]

Posted on November 02, 2017 at 21:37

[E T]

Posted on May 02, 2018 at 16:51

>

replaced the firmware with a port of the LRWAN tree.

Is there a chance you could share that port? The FW on the shield I've got is totally useless, I can't even AT+VER it all i get, and I quote: '

ERROR_UNKNOW_COMMAND'.

Also I thought the JTAG pins on the shield would be enough to reprogram it with their newer HEX images, but I'm unable to unlock it. It says write-protected:

openocd -s scripts \

-f interface/stlink-v2-1.cfg \

-f target/stm32l0.cfg -c 'init' -c 'stm32lx unlock 0'

Open On-Chip Debugger 0.0

Licensed under GNU GPL v2

For bug reports, read

https://community.st.com/external-link.jspa?url=http%3A%2F%2Fopenocd.org%2Fdoc%2Fdoxygen%2Fbugs.html

Info : auto-selecting first available session transport 'hla_swd'. To override use 'transport select <transport>'.

adapter speed: 300 kHz

adapter_nsrst_delay: 100

Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

none separate

Info : Unable to match requested speed 300 kHz, using 240 kHz

Info : Unable to match requested speed 300 kHz, using 240 kHz

Info : clock speed 240 kHz

Info : STLINK v2 JTAG v28 API v2 SWIM v17 VID 0x0483 PID 0x374B

Info : using stlink api v2

Info : Target voltage: 3.262351

Info : stm32l0.cpu: hardware has 4 breakpoints, 2 watchpoints

Info : Device: STM32L0xx (Cat. 3)

Info : STM32L flash size is 64kb, base address is 0x8000000

Error: access denied / write protected

STM32Lx unlock failed

I'm using the F3 discovery's programmer following this instructions:

https://jeelabs.org/book/1547a/

, so not sure if I missed some wiring or need to set some switches differently.