cyclic memory section dependency with section .fs_data_run

RE: cyclic memory section dependency with section .fs_data_run

Shiba Inu — Sat, 02 Sep 2017 04:09:06 GMT

I ended up deciding to use the S132 soft device. It worked on first setup, per the Segger Embedded Studio blog post.

RE: cyclic memory section dependency with section .fs_data_run

Mark.Thielen — Fri, 01 Sep 2017 12:13:28 GMT

I had the same problem. Make sure you have the same ordering of your sections in FLASH and RAM. I see your .fs_data_run is on bottom of the other sections (.fast_run, .data_run, .tdata_run) in FLASH but in RAM it is on top.

RE: cyclic memory section dependency with section .fs_data_run

Shiba Inu — Fri, 01 Sep 2017 07:50:20 GMT

I commented out (the portion in bold) in nrf_atfifo.c

define STATIC_ASSERT(EXPR)
//extern char (_do_assert(void)) [sizeof(char[1 - 2!(EXPR)])]

RE: cyclic memory section dependency with section .fs_data_run

bjorn-spockeli — Fri, 01 Sep 2017 07:25:54 GMT

Even before that, I was receiving errors referring to "variably modified 'do_assert' at file scope" as is similarly described here by another devzone user, however I commented our erroneous declaractions (a compiler assert definition):

What did you comment out?

RE: cyclic memory section dependency with section .fs_data_run

Shiba Inu — Thu, 31 Aug 2017 20:09:58 GMT

I now am getting just the following error: 'cyclic memory section dependency with section .fs_data_run'

RE: cyclic memory section dependency with section .fs_data_run

Shiba Inu — Thu, 31 Aug 2017 16:56:40 GMT

Thank you for your response! I have moved beyond the .fs_data error it seems. I have also included the lines addressed in your linked solution.

Now, my problem is the 'undefined reference to...' errors. Do you know how to address those?

Please take a look at that last flash_placement.xml I linked in my question.

RE: cyclic memory section dependency with section .fs_data_run

bluez — Thu, 31 Aug 2017 14:45:33 GMT

The .fs_data is not defined in the flash_placement.xml, hence it's place in the UNPLACED_SECTIONS. Following the solution from: devzone.nordicsemi.com/.../ should work.