This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Need help on NRF9160 Development of Hardware & firmware

hello,

we are developing a product, in which it needs BLE, LTE,GPS. we are planning to choose Nrf9160 for LTE & GPS. we need following support during development

1. what is the best suitable antenna for NRF9160 for both LTE & GPS, we don't  have hardcore RF expertise, so we need help on this , we have some flex antennas 

  a.https://www.molex.com/molex/products/part-detail/antennas/2072350100

 b.https://www.molex.com/molex/products/part-detail/antennas/2065600100

 can above antennas be used by just connecting via UFL connector with out any matching components etc , or any smaller chip antenna available

2.what is the smallest size PCB we can have when NRF9160 with including antennas . remaining BLE & power circuits we can manage

3. we are not interested in 2 firmware for 9160 separately and ble separately. so we are planning to choose BLE processor as main MCU , and NRF9160 will be used with out any custom firmware, so AT command based. so any suggestions on this

4.  our goal will be to extract the GPS from 9160 to BLE main mcu, and then send it via MQTT. does NRF9160 supports MQTT, any code examples via AT. with out implementing MQTT protocol on BLE main mCU, does NRF9160 supports any quick command. as of now, only publishing, in future might need subscribe also.

5. Does NRF9160 modules selling in online have embedded sim enabled, if so how to activate it with carrier.

6. lets say, if LTE is connected to carrier, then with out disconnecting from carrier, can we get GPS information, if so how?  any examples.

we are already running late to finalize the module.need help from Nordic officials.Thank you

with regards

Dr.N.Chandra sekhar, Phd

Parents
  • HELLO heidi.

    thanks for reply, i do consider MR.carls inputs. thanks for both. i am starting with antenova gps active antenna for GPS, and molex felxstrip for LTE,

    this is the first time i am handling nrf9160,and we are already running late, so i need some support privately and guide me in every aspect, so we can take this to production in less than 3 months.as we already got screwed bcz of corona.

    with respect to BLE , we are planning to use other vendor module with AT commands , will it be easier to do all BLE stuff from the nrf9160 via uart, or do you recommend to use nordic module only. ?

    we are planning to use Esim. but we dont know how to proceed. dont know where to start, Does netwrok operators provide esim? or do we need to use any balnk esim modules and then load with imei or how,this works can you guide me on this?

    i had tried installing NCS and followed step by step getting started guide, but still unable to get a clear idea about , how to create a empty project, or any empty or template project to start with. like in BLE empty

    Thank you

  • Hi!

    The reason I suggest using nRF9160 as the main MCU and handle BLE over UART is that there are a lot of sample projects in NCS for exactly this setup. 

    With regard to eSim, I suggest asking your network provider about how this is provided. I will try to find someone tomorrow who has knowledge about how eSIM's work, as today is a Norwegian holiday. Since the Nordic modules (DK and Thingy) don't support this I don't have much experience with it. 

    For a blank NCS project, you need the following file structure

    -src
        -main.c
    -prj.conf
    -CMakeLists.txt

    where prj.conf is for all your configurations, and CMakeLists.txt looks something like this

    cmake_minimum_required(VERSION 3.8.2)
    
    include($ENV{ZEPHYR_BASE}/../nrf/cmake/boilerplate.cmake)
    include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
    project(NONE)
    
    # NORDIC SDK APP START
    target_sources(app PRIVATE src/main.c)
    # NORDIC SDK APP END

    If you go to ncs/nrf/samples/nrf9160 you'll find a lot of sample applications. We usually recommend newcomers start by editing an application that resembles theirs, instead of creating a blank project. This git-repo, from a colleague, also has a few basic samples, such as UART and SPI to show how to set up these things.

    As for your request to guide you in every aspect, the way we handle technical support on DevZone is generally to make a new ticket if your follow-up questions are not related to the original ticket. This is first and foremost so that other users can easily find tickets similar to their own and to make the website searchable. And secondly, to make sure your questions end up with the Nordic engineer who has experience with what you're asking about.

    Lastly, so you're aware, we do offer hardware review of your design and antenna tuning for free, when you have gotten that far in your development process. :) 

    Best regards,

    Heidi

  • Hi!

    Yes, you need to get the eSIM from your network provider. 

    The COEX0 is a part of the LTE modem coexistence interface, which is a three-pin interface for RF interference avoidance towards a companion radio device while MAGPIO0 is part of the LTE modem RF control external interface, a digital interface for controlling external RF applications.

    So the COEX0 is an input to the LTE modem from an external device, and when active high, indicates that the external device transceiver is turned on. If you're using the internal GPS, COEX0 can be used as active high to control for the external LNA component.

    The MAGPIO pins allow the modem to control external circuitry, and specifically, the MAGPIO0 is used to enable the GPS LNA. 

    So, you should use the MAGPIO0 to control the GPS LNA. 

    Best regards,

    Heidi

  • Hi Heidi,

    Thanks for your kind support till date. i had completed Hardware sch & layout. how can i submit it for review privately. thank you

  • Great! Just make another ticket on DevZone for the hardware review, and make sure to make it private

    Best regards,

    Heidi

  • Hi,

    Thank you, yes files shared for review in another ticket.

    now its turn to start work on firmware.

  • Hello Heidi,

    we finished assembling our first pcb with nrf9160. right now i am trying to upload the "asset tracker"firmware. we dont have nrf9160 dk. we are using a SIP custom board. i have few NRF52DK. i am trying to connect it via the Jlink of nrf52dk. but i am getting error that " the connected Jlink does not support Arm v8 arhchitecture and can not be debugged"

    how can i program the nrf9160 device with the help of jlink which comes with nrf52dk.  but i see that, it detects the NRF9160 .please help me over it.thank you

Reply
  • Hello Heidi,

    we finished assembling our first pcb with nrf9160. right now i am trying to upload the "asset tracker"firmware. we dont have nrf9160 dk. we are using a SIP custom board. i have few NRF52DK. i am trying to connect it via the Jlink of nrf52dk. but i am getting error that " the connected Jlink does not support Arm v8 arhchitecture and can not be debugged"

    how can i program the nrf9160 device with the help of jlink which comes with nrf52dk.  but i see that, it detects the NRF9160 .please help me over it.thank you

Children
No Data
Related