This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Gazell does not work with nrf 52832

Nice to meet you.

The chip uses nRF 52832. MDK keil μVision V 5.22.0.0 is used as the development environment.

Since I confirmed the operation with the sample project using the nRF 52 Development Kit, I am planning to develop nRF 52832 on my board.

I would like to use gazell to communicate between the master and slave, I have created a new project, but gazell's library does not work well.

I chose gzll and nrf_gzp in Manage Run-Time Environment and include "nrf_gzll.h"

nrf_gzll_init (NRF_GZLL_MODE_HOST);

If you try to run the program will not proceed any further. (I will paste the screen of the stopped place) image description Please teach me.

Parents
  • You should probably respond to the previous comment, since I think Mr. Bui is a Nordic employee. That said, the program has entered an infinite loop at "B ." which in assembly language means "branch to the current program counter address" i.e. branch back to this instruction. This particular loop is part of the default handler, to which many interrupt vectors point to unless you substitute your own handler (overriding the "weak" definition.) Since many vectors point to the same handler, you don't know which device was causing the interrupt. Are you are using other devices than the ones that the gazelle code probably uses (e.g. the RADIO_IRQ_Handler) and did you provide an interrupt handler?

Reply
  • You should probably respond to the previous comment, since I think Mr. Bui is a Nordic employee. That said, the program has entered an infinite loop at "B ." which in assembly language means "branch to the current program counter address" i.e. branch back to this instruction. This particular loop is part of the default handler, to which many interrupt vectors point to unless you substitute your own handler (overriding the "weak" definition.) Since many vectors point to the same handler, you don't know which device was causing the interrupt. Are you are using other devices than the ones that the gazelle code probably uses (e.g. the RADIO_IRQ_Handler) and did you provide an interrupt handler?

Children
No Data
Related