• State Not Answered
  • Replies 15 replies
  • Subscribers 65 subscribers
  • Views 1168 views
  • Users 0 members are here
Attachments (6) Download All
Nordic Case Info
  • Case ID: 308944
Options

My app is not working on all nrf52810 existing modules

Jean-marie

Hello, I developed a simple advertising application first on nrf52832 with succéss and I'm trying to adapt it to nrf52810.
I therefore switched from S132 to the S112 softdevice and the application works on the NRF52DK dev board, but also on a "Minew" MS50SFA module (with 32.768 Khz crystal).
On the other hand, on a "MOKO - M2" module which does not have this crystal, it does not work!
I however modified the lines corresponding to the presence or not of this crystal in the sdk-config.h!
What did I forget?

I'm working on SEGGERS

Thanks for your help

Jiemde

Parents Reply Children
  • 0 in reply to Jean-marie

    Hi,

    Ok I wasn't aware that this was actually an already product, I thought by module you meant an already pre certified nRF52810.

    1. Could you define what you mean by "it doesn't work"?
    2. What application are you using for scanning the advertising, are you using nRF Connect app or the module makers "Moko-Standard-app"?
    3. Have you tried using the debugger and see if the program asserts? Does it stop anywhere? 
    Jean-marie said:

    Here are files

    MOKO Standard APP User Maunal_V1.1_20220301.pdf

    I was looking for the schematics,

    Jean-marie said:
    We have some units with the 3 axes option ( but we don't use it ) and no 32.768 Khz crystal and it's an nrf52810 soc  in place of the nrf52811 but it's the right schematic ;))

    Could you elaborate on this? Did you replace the nRF52811 included with the module with a nRF52810? How did you verify that it didn't have a low frequency crystal?

    suggestion:

    You can try to adjust the NRF_SDH_CLOCK_LF_ACCURACY, try the other options such as 250 ppm, 50 ppm, and 1 ppm and see if it helps,

    regards
    Jared 

  • 0 in reply to Jared

    Hi Jared, thank for your fast reply.

    1. No advertising
    2. I use nRF Connect app
    3. No, I don't replace the nRF82811 by the nRF52810 myself ( it where made like this by MOKO ), see the picture and you can see that there is no 32.768 Khz crystal and it's an nRF52810 soc

    InkedIMG_20230606_101607.pdf

    Will try your suggestion.

    Question about the flashing:

    Must I use a specific RAM START and FLASH START address ?

    I keep you informed about the tests

    Best regards

    Jiemde

  • 0 in reply to Jean-marie

    Hello Jared,

    I've try all the options ( 12 ) of the NRF_SDH_CLOCK_LF_ACCURACY but without success!

    It's like the nRF52810 cannot run in R/C mode or like the sdk_config has no action on the soc config !

  • 0 in reply to Jean-marie

    Hi,

    Jean-marie said:
    No, I don't replace the nRF82811 by the nRF52810 myself ( it where made like this by MOKO ), see the picture and you can see that there is no 32.768 Khz crystal and it's an nRF52810 soc

    Ok, Yes I can see from the picture that you shared that it doesn't have a LFXO crystal and that it is a nRF52810. Which is weird since it's not specified by the product brief you've shared. 

    Jean-marie said:
    Must I use a specific RAM START and FLASH START address ?

    The program should assert if the memory settings aren't right,

    Jean-marie said:
    No advertising

    But does the program assert? Have you connected a debugger and see if the program reach the advertising function without error? Does it return successfully?

    regards

    Jared 

  • 0 in reply to Jared

    Hello Jared, hope you are well.

    I've do an experience: Take an M2 ( without 32.768Khz crystal ) and flash it with a sdk_config.h configured for using the internal R/C. and of course it don't work! - power OFF !

    I've installed an 32.768 Khz crystal and the 2 capacities, then power ON ! ........... It work !

    So I think that the config do nothing !

    Can you explain that ?

    Thanks for your reply

    Jiemde

Related