ZED-F9P SPI: DSEL jumper has no effect

GPS/GNSS Development Boards
11

Hi Scott & Paul,

OK… Some updates for you…

I started writing the GNSS SPI logger example and couldn’t get the GNSS to begin on SPI. I started looking back through the SPI examples I wrote a while ago and found this cryptic “note to self”:

https://github.com/sparkfun/SparkFun_u- … no#L42-L45

The SPI examples themselves are here:

https://github.com/sparkfun/SparkFun_u- … amples/SPI

I configured my SPI logging example so it would keep attempting to begin:

  // Connect to the u-blox module using SPI port, csPin and speed setting
  // ublox devices generally work up to 5MHz. We'll use 4MHz for this example:
  bool begun = false;
  do
  {
    begun = myGNSS.begin(SPI, GNSS_CS, 4000000);
    if (!begun)
    {
      Serial.println(F("u-blox GNSS not detected on SPI bus. Please check wiring."));
      delay(1000);
    }
  }
  while (!begun);

I left that running while I connected to the ZED-F9P using u-center over USB.

I opened up “Messages View” and selected UBX \ CFG \ PRT (Ports).

I set Protocol In and Protocol Out to “None” on both 0-I2C and 1-UART1. (Click “Send” to apply each change.)

Still no joy.

I set Protocol In and Protocol Out to “0+1+5 UBX+NMEA+RTCM3” on 4-SPI…

Hey presto! The GNSS began and I could communicate with it.

So it appears that the SPI port needs a kick to enable the UBX messages / protocol.

I’ll try saving the configuration into BBR and see if I can still begin the GNSS after power-cycling it. It would be nice not to have to mess about with CFG PRT each time…! :smiley:

I’ll post an update later.

I hope this gets you going!

Paul