This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Actinius Icarus nrf9160 issue with asset tracker

Hi,

I have managed to upload the asset tracker via mcuboot to my Actinius Icarus.

It should straight-up connect to the actinius.io cloud, but when I check the link monitor it keeps running loops and fails to connect to LTE.

It keeps giving me "Response buffer not large enough" errors.

Any idea where this comes from and how to fix this?

***Board information***



Application version: 1.4.0
Modem firmware version: mfw_nrf9160_1.2.3

[J[00:00:14.486,572] <inf> app: The device is registered on actinius.io
[J
[J[00:00:43.800,964] <inf> app: GPS search initiated
[J[00:00:43.801,086] <inf> app: Requesting AGPS Data
[J[00:00:44.800,262] <inf> app: GPS operation is blocked, waiting for LTE window
[J


ip 8efb:5c0::300:ae11:2f00:2f00 (c005fb8e) port 7276


Starting SUPL session
[1B
[1D
[J[00:00:45.757,476] <err> at_cmd: Response buffer not large enough
[J[00:00:45.757,537] <err> supl_client: Fetching LTE info failed
[J[00:00:45.757,690] <err> os: ***** BUS FAULT *****
[J[00:00:45.757,690] <err> os:   Precise data bus error
[J[00:00:45.757,690] <err> os:   BFAR Address: 0x4fbd3820
[J[00:00:45.757,720] <err> os: r0/a1:  0x20022b80  r1/a2:  0x00000001  r2/a3:  0x0000001a
[J[00:00:45.757,720] <err> os: r3/a4:  0x4fbd3820 r12/ip:  0x20032c90 r14/lr:  0x00035b53
[J[00:00:45.757,720] <err> os:  xpsr:  0x01000000
[J[00:00:45.757,751] <err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
[J[00:00:45.757,751] <err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000
[J[00:00:45.757,781] <err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
[J[00:00:45.757,812] <err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
[J[00:00:45.757,812] <err> os: fpscr:  0x20032ed4
[J[00:00:45.757,812] <err> os: Faulting instruction address (r15/pc): 0x00035bea
[J[00:00:45.757,843] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[J[00:00:45.757,873] <err> os: Current thread: 0x20021f90 (workqueue)
[J[00:00:45.874,328] <err> fatal_error: Resetting system
[J[00:00:00.201,751] <inf> board_control: e.s selected
[J[00:00:00.204,193] <inf> app: ** Starting the Actinius Asset Tracker Firmware
[J[00:00:00.205,871] <inf> app: Press the user button on the board to start the shell...





[J


...




Kind regards,

Thomas

Parents
  • Hi Thomas,

    From your log it seems that the device is successfully connecting both to the LTE network and to actinius.io, as it reports that it is registered (app: The device is registered on actinius.io). The crash seems to be coming from the SPUL library that takes care of the A-GPS data. In any case, since this firmware is built by Actinius, I would suggest that you send an email to [email protected] with a full log as above, and information such as the network (if you know it, otherwise just the area of operation) and my colleagues will get to the bottom of it.

    Thank you.

    BR,

    Mike

Reply
  • Hi Thomas,

    From your log it seems that the device is successfully connecting both to the LTE network and to actinius.io, as it reports that it is registered (app: The device is registered on actinius.io). The crash seems to be coming from the SPUL library that takes care of the A-GPS data. In any case, since this firmware is built by Actinius, I would suggest that you send an email to [email protected] with a full log as above, and information such as the network (if you know it, otherwise just the area of operation) and my colleagues will get to the bottom of it.

    Thank you.

    BR,

    Mike

Children
No Data
Related