nrf52833 P0.0 will output high level strangely

RE: nrf52833 P0.0 will output high level strangely

Simonr — Fri, 30 Jul 2021 07:15:05 GMT

Glad you got to the bottom of this issue. Great detective work!

RE: nrf52833 P0.0 will output high level strangely

zk017 — Fri, 30 Jul 2021 03:41:41 GMT

OK，it's solved! NRF_DRV_PWM_PIN_NOT_USED was missed out.@Simonr, thank you very much!

RE: nrf52833 P0.0 will output high level strangely

zk017 — Wed, 28 Jul 2021 08:38:45 GMT

devzone.nordicsemi.com/.../4786.main.c

RE: nrf52833 P0.0 will output high level strangely

Simonr — Tue, 27 Jul 2021 13:04:26 GMT

Please note that you also have to short SB3 and SB4 to get an output to P0.00 (and P0.01) as well.

For me to test your application, can you upload the entire main.c file (or just the .hex file you have) so I can test the same application you have on a DK on my end.

Best regards,

Simon

RE: nrf52833 P0.0 will output high level strangely

zk017 — Tue, 27 Jul 2021 02:16:46 GMT

cut off SB1 and SB2 here. You can make a try use keil add my code above, run the program and to test P0.0 level when executed function nrf_drv_pwm_simple_playback(&m_pwm0, &m_pwm_seq, 1, NRF_DRV_PWM_FLAG_LOOP).

RE: nrf52833 P0.0 will output high level strangely

Simonr — Mon, 26 Jul 2021 06:28:20 GMT

How do you disconnect the 32.768kHz crystal exactly? And are you sure that the corrects packs are installed in your Keil µVision project?

Best regards,

Simon

RE: nrf52833 P0.0 will output high level strangely

zk017 — Fri, 23 Jul 2021 07:08:41 GMT

All of my operations are correct， the strang thing exist, so it confused me. You can use PCA10100 demo board to do a test. (I disconnect the 32k xtal with p0.0.)

RE: nrf52833 P0.0 will output high level strangely

Simonr — Fri, 23 Jul 2021 06:18:09 GMT

It should work as intended with Keil µVision as well, and you should be able to use your preferred IDE for development. Does the project compile and flash successfully with Keil µVision? Are you sure that the application is flashed with the SoftDevice correctly when using Keil? I see no reason why Keil wouldn't work while SES does.

Best regards,

Simon

RE: nrf52833 P0.0 will output high level strangely

zk017 — Thu, 22 Jul 2021 02:30:20 GMT

no other reason, I used to use keil in the past. Do you say that the new SDK supports better with ses， we have to use ses to compile the sdk17.02+52833 in the future?

RE: nrf52833 P0.0 will output high level strangely

Simonr — Wed, 21 Jul 2021 12:56:41 GMT

So your application (and P0.00) works as expected if you compile and flash the project in SES but not in Keil? Is there any particular reason you're using one over the other?

Best regards,

Simon

RE: nrf52833 P0.0 will output high level strangely

zk017 — Wed, 21 Jul 2021 02:15:18 GMT

my settings of these macros is same as yours. We have found use keil to compile there exist this question(P0.0 output high strangly), but use ses compile is ok. It's confused us.

RE: nrf52833 P0.0 will output high level strangely

Simonr — Tue, 20 Jul 2021 11:49:35 GMT

Hi P0.00 (and P0.01) is by default in our examples used by the external 32.768 kHz LF crystal which is present on our DKs, but not on most 3rd party modules and might not be used on your HW. If you'd like to use the P0.00 as a normal GPIO, you need to configure your device to use the internal RC oscillator. This can be done by changing the following defines to these values in your sdk_config.h file.

// <h> Clock - SoftDevice clock configuration

//==========================================================
// <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// <0=> NRF_CLOCK_LF_SRC_RC 
// <1=> NRF_CLOCK_LF_SRC_XTAL 
// <2=> NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// <0=> NRF_CLOCK_LF_ACCURACY_250_PPM 
// <1=> NRF_CLOCK_LF_ACCURACY_500_PPM 
// <2=> NRF_CLOCK_LF_ACCURACY_150_PPM 
// <3=> NRF_CLOCK_LF_ACCURACY_100_PPM 
// <4=> NRF_CLOCK_LF_ACCURACY_75_PPM 
// <5=> NRF_CLOCK_LF_ACCURACY_50_PPM 
// <6=> NRF_CLOCK_LF_ACCURACY_30_PPM 
// <7=> NRF_CLOCK_LF_ACCURACY_20_PPM 
// <8=> NRF_CLOCK_LF_ACCURACY_10_PPM 
// <9=> NRF_CLOCK_LF_ACCURACY_5_PPM 
// <10=> NRF_CLOCK_LF_ACCURACY_2_PPM 
// <11=> NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif

Best regards,

Simon