Hello,
I have a writing problem when using pic,
An error occurs when using a pointer to access a function in a global variable. The reason is that the function address in the global variable has been determined, but when using a pointer to access it, pic will not add the offset for me.

If you update the contents of .data during the system initialization phase, you cannot accurately distinguish which ones are absolute addresses and which ones are data.

example:

typedef void (*func)(void);

struct ops
{
  uint32_t a;
  func b;
};
void test(void)
{
  //do nothing
}

struct ops g_ops =
{
  12345,
  test
};

int main(void)
{
  struct ops *ops = &g_ops;

  ops->b();
  return 0;
}

do ops->b() will get a bad address.

SRAM remapping is now done on bootloader side. This is wrong. Put it to firmware side, C init function.

Hello. I use your example on the stm32l051 chip. For floating point numbers, the linker supplies calls like __aeabi_fmul. There is an assumption that they are "broken" any such call breaks the execution of the program. Do you have any ideas about this?