• State Not Answered
  • Replies 6 replies
  • Subscribers 25 subscribers
  • Views 190 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290468
Options

For the "BASE0/1" in the doc of infocenter: does it mean the address before "addr_conv", or after?

user26625

Hi,

I'm using SDK v14.2.0.

For the workaround of [107] RADIO: Immediate address match for access addresses containing MSBs 0x00

I'm trying to avoid the addresses in the list, then I found there is a function "addr_conv" when Nordic set my 4-byte address (like: 0x11,0x22,0x33,0x44) to registers "BASE0/1", and it converts the address to like: 0x8844CC22.

So my question are:

  • When this workaround saying that "pls avoid BASE0=0x0000XXXX", this "0x0000XXXX" is the one before "addr_conv", or after?
  • My scenario is: BASE0/1 are set by app, so I need provide these addresses to our app to avoid the "NRF_ERROR_INVALID_PARAM" of "nrf_esb_set_base_address_0/1", if these addresses are the ones after "addr_conv", then I have to also provide the function "addr_conv", right?

Thanks!

Parents
  • 0

    Hi Kenneth,

    Thanks, actually my question is just from what you suggested to look at: "nrf_esb_set_base_address_0/1" and its callee "addr_conv".

    Let me adjust my question to be:

    • What input parameter "p_addr" should I avoid when calling "nrf_esb_set_base_address_0/1", to avoid the "NRF_ERROR_INVALID_PARAM" error, when I'm using 52832 revision 1 and SDK V14?
    • Are they just the ones in the workaround of erratas, like "BASE0=0x0000XXXX" ? Or I need to calculate the forbidden addresses by myself with these "0x0000XXXX" and a "opposite operation" of "addr_conv"?

    Thanks!

  • 0 in reply to user26625

    In this specific case we have provided a descriptive errata explaining the issue and which addresses to avoid, we have also provided source code for the ESB protocol that show how the code can test if the address is affected by the issue, and if it is affected the api will return NRF_ERROR_INVALID_PARAM. I think this issue is well documented, along with code that can test for this issue.

    Edit: The addr_conv() does not change the address, it's only used internallly in nrf_esb_set_base_address_0/1 to change the byte order of the address to be able to test if the address is affected by the issue.

    Kenneth

Reply
  • 0 in reply to user26625

    In this specific case we have provided a descriptive errata explaining the issue and which addresses to avoid, we have also provided source code for the ESB protocol that show how the code can test if the address is affected by the issue, and if it is affected the api will return NRF_ERROR_INVALID_PARAM. I think this issue is well documented, along with code that can test for this issue.

    Edit: The addr_conv() does not change the address, it's only used internallly in nrf_esb_set_base_address_0/1 to change the byte order of the address to be able to test if the address is affected by the issue.

    Kenneth

Children
No Data
Related
Terms of service