RAK3172 MIC mismatch

LPWAN Modules / EVBs RAK3172
#1

After resetting to defaults and going step by step as described still the error “MIC mismatch” comes up.

I used this documentation to set things up: RAK3172 Module Quick Start Guide | RAKwireless Documentation Center

See the commands and values I typed in.

RAK3172-MIC-mismatch
RAK3172-MIC-mismatch1001×2227 302 KB

Here you can see the packet that arrived at the gateway (RAK7268).

(see screenshot above)

Here you can see what the TTN log says.

(see screenshot above)

Here you can see what the packet decoder tells us.

https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=ADMRMxEzETMRRCKIRCKIRCLVZsg67SA%3D&nwkskey=&appskey=11112222333344445555666677778888

(see screenshot above)

To me it looks like the MIC is wrong as calculated by the module.

Is there a firmware update under way? What can I do about this? Thank you.

p.s. I have also a MIC mismatch when using the network server functionality of the RAK7268. So it does not seem to be an issue with TTN.

#2

MIC mismatch error is usually caused by the APPKEY.

I suggest you try to generate a new APPKEY and use that on your RAK3172. You can generate a new one under Join Settings in the General Settings tab of your TTN device console

image
image731×670 38.8 KB

Another thing you can do is to reset the device using ATZ command after setting the EUIs/KEY and before joining the network.

#3

I went through the process many times without success.

BUT to reboot the module with ATZ did SOLVE it.

So these were the steps…

ATR
AT+NWM=1
AT+NJM=1
AT+CLASS=A
AT+BAND=4
AT+DEVEUI=70...39
AT+APPEUI=0000000000000000
AT+APPKEY=02...62
ATZ
AT+JOIN=1:0:10:8
OK
+EVT:JOINED

There seems to be that bug that joining is possible only after rebooting the module after setting the APPKEY. That’s somehow annoying but NEVERTHELESS it WORKS that way! I could not find any hint on that in the documentation. Thank you for the advice. I assume this will be the cause of many problems or seemingly erratic behaviour.

Have a nice weekend. Cheers.
Thomas

1 Like
#4

Good thing it works. We have new RAK3172 FW that is based on RUI3. I never experience this issue anymore. I suggest you update your firmware and see if things will improve.

There are minor differences on the old RAK3172 FW and the RUI3 though.

#5

Thank you. We can close.

#6

Sorry. One last thing… where is the newest firmware supposed to be?

I only found RAKwireless Downloads

And there it seems to be RAK3172_v1.0.4_App_20220218.bin - i.e. version 1.0.4.

But here (RAK3172 Module AT Command Manual | RAKwireless Documentation Center) it says that 1.0.4 was deprecated.

Could you please clarify. Thank you.

#7

Hi @tb4450 ,

Please follow this DFU guide. The links are updated and will send you to the right links.

The updated RAK3172 FW is now based on RUI3.

RUI3 is a firmware platform we created so we can unify the firmware of our devices regardless of chipsets. Also, it allows you to compile firmware directly on the device and not relying on the AT commands and external host MCU.

#8

Thank you. All went fine. I could upgrade and test OK.

What you mention about RUI3 that allows to compile firmware directly is very interesting. I will have a look.

Finally, we are done here. Thanks.