My application board do not run example project

RE: My application board do not run example project

Di-sheng — Thu, 08 Oct 2020 22:35:16 GMT

Hi Mttrinh

The light-switch server works very well on my application board now.

Thanks,

B,Rs

Di-sheng

RE: My application board do not run example project

Di-sheng — Thu, 08 Oct 2020 16:54:15 GMT

Hi Mttrinh

Oh! Yes. I miss that.

Thanks,

B,Rs

Di_sheng

RE: My application board do not run example project

Mttrinh — Thu, 08 Oct 2020 13:30:35 GMT

[quote user="SpongeBob"]Is there any mechanism to prevent chip reads and writes, how to do it and how to unlock it ?[/quote]

Have a look at Edvin's answer in this thread.

[quote user="SpongeBob"]I did not find the "m_button_handler_cb(i)" code in whole sulotion and nordic webs. Would you can help me to find it. I want to know what does it.[/quote]

m_button_handler_cb is the callback function for the buttons.

Looking in hal_buttons_init(hal_button_handler_cb_t cb), you can see that m_button_handler_cb is set to cb. In main.c, hal_buttons_init is called with button_event_handler as argument which means that m_button_handler_cb is equal to the button_event_handler. You can find button_event_handler(...) in main.c

RE: My application board do not run example project

Di-sheng — Thu, 08 Oct 2020 00:36:05 GMT

Hi Mttrinh

I add the 32kHz crystal and the dfu code running correct now. I will try to run the light-switch server code tomorrow.

I have other question about the code of the light-switch server example:

I read the code of simple_hal.c, showed below:

/*****************************************************************************
* IRQ handler(s)
*****************************************************************************/

#if BUTTON_BOARD
void GPIOTE_IRQHandler(void)
{
NRF_GPIOTE->EVENTS_PORT = 0;
for (uint8_t i = 0; i < BUTTONS_NUMBER; ++i)
{
/* Check that the event was generated by a button press, and reject if it's too soon (debounce).
* NOTE: There is a bug with this at the wrap-around for the RTC1 where the button could be
* pressed before HAL_BUTTON_PRESS_FREQUENCY has passed a single time. It doesn't matter practically.
*/

////////////2020-0828 button debug start
#if defined(BOARD_PCA10059) && !defined(BOARD_LSM100)
if ((~NRF_GPIO1->IN & (1 << (m_buttons_list[i]))) &&
TIMER_DIFF(m_last_button_press, NRF_RTC1->COUNTER) > HAL_BUTTON_PRESS_FREQUENCY)
#else
if ((~NRF_GPIO->IN & (1 << (m_buttons_list[i]))) &&
TIMER_DIFF(m_last_button_press, NRF_RTC1->COUNTER) > HAL_BUTTON_PRESS_FREQUENCY)
#endif ////////////2020-0828 button debug end
{
m_last_button_press = NRF_RTC1->COUNTER;
m_button_handler_cb(i);
}
}
}
#endif

I did not find the "m_button_handler_cb(i)" code in whole sulotion and nordic webs. Would you can help me to find it. I want to know what does it.

Thanks,

B,Rs,

Di-sheng

RE: My application board do not run example project

Di-sheng — Tue, 06 Oct 2020 17:34:12 GMT

Hi Mttrinh

Thanks for your replay.

Yes, I have realized that the lack of 32.768kHz crystal may be the root of the problem. I can get parts today .

You are right. Is there any mechanism to prevent chip reads and writes, how to do it and how to unlock it ?

Thanks!

B,Rs

Di-sheng

RE: My application board do not run example project

Mttrinh — Tue, 06 Oct 2020 14:13:51 GMT

Hi,

Can you check if your module have a 32khz crystal? It might be the reason for the issues you are seeing if you are missing this.

[quote user=""]Is there any key to lock the flash so that the application code can not be write to flash?[/quote]

Do you mean like preventing reprogramming?