How to verify that the 32MHZ crystal is actually working (nRF52832?

[abdosalm]

I am using nRF connect SDK v2.9.0 with a custom developed board that looks like this:

I tried the 'Bluetooth LE LED Button service' sample as it's and noticed that nothing was working. I grapped my logic analyzer and hooked it up onto the 32MHZ but nothing is showing. I mean other functionalities like zepyrRTOS, PWM, GPIOs, I2C, etc...  are working successfully but not BLE.

does the nRF52832 have an internal clock through which it works by default and if so, how does it use the external clock. what is the first thing to debug?

this is the crystal I am using:

https://www.lcsc.com/product-detail/Crystals_YXC-Crystal-Oscillators-X322532MOB4SI_C9009.html 

and these are the schematics:

[Turbo J]

Most of the BTLE example code is intended for the DK which has both crystals (32MHz and 32kHz) populated.

You have to modify them in order to only use the 32 MHz one. Details can be found in the documentation.

[abdosalm]

Actually, as illustrated in the schematics, there is a 32KHZ crystal populated on the board. I didn't see if it's working or not. but still don't know why the 32MHZ crystal isn't working.

[abdosalm]

Edit: the populated 32KHZ crystal is working but with a small defect, the PK-PK voltage is ~256mV only. I don't know if this is natural or not.

[abdosalm]

Another Edit: 

the 32MHZ crystal is also working but not all the time and the PK-PK voltage is around ~345mV only.

[abdosalm]

I actually don't know what to debug next,

maybe the ground loop is too big so that the PK-PK is ~356mV only, maybe the oscilloscope is introducing extra capacitance for the crystal preventing it from reaching the 3V3, or maybe it's normal for the crystal to have a PK-PK voltage of ~356mV, IDK.

[abdosalm]

EDIT: I found something interesting, but I am still trying to understand what this error means: