Access Window code works on IAR project but not GNU project

I successfully tested setting and clearing the Access Window on a small Synergy S5D9 project on a PK-S5D9 evaluation board. This project was built with the IAR toolchain. My colleague could not get the same Access Window code to work on his S5D9 project that was built using the Gnu toolchain. He is getting a 0x2B error from SSP: SSP_ERR_INVALID_HW_CONDITION.

The SSP User Guide says this error can be avoided by making sure DTC/DMAC, EDMAC, or LCDC/2DG/JPEG are enabled. None of these are enabled in his code. Per the User Guide, he also defined R_FLASH_HP_CHECK_MODULE_STOP_BITS to 0, and called the recommended code

ssp_err_t err;
ssp_feature_t ssp_feature = {{(ssp_ip_t) 0U}};
ssp_feature.id = SSP_IP_DTC;

err = R_BSP_ModuleStopAlways(&ssp_feature);

He seems to be doing everything right but keeps getting the 0x2B error. (My project also got the 0x2B error at the beginning before I followed the User Guide recommendations).

Could this problem be due to his using gcc instead of IAR?

Thanks.

Parents
  • The SSP V2.6.0 Users manual shows for the return value SSP_ERR_INVALID_HW_CONDITION :-

    The configuration area cannot be written
    while DTC/DMAC, EDMAC, LCDC/2DG/JPEG
    are enabled.

    This is to prevent prohibited
    memory accesses while the flash sequencer
    is running. Refer to the technical update
    number TN-SY*-A033A/E.

    This check can be disabled by defining
    R_FLASH_HP_CHECK_MODULE_STOP_BITS to
    0.

Reply
  • The SSP V2.6.0 Users manual shows for the return value SSP_ERR_INVALID_HW_CONDITION :-

    The configuration area cannot be written
    while DTC/DMAC, EDMAC, LCDC/2DG/JPEG
    are enabled.

    This is to prevent prohibited
    memory accesses while the flash sequencer
    is running. Refer to the technical update
    number TN-SY*-A033A/E.

    This check can be disabled by defining
    R_FLASH_HP_CHECK_MODULE_STOP_BITS to
    0.

Children