Now that I have found the differences between the pin_data.c files in both projects, a strange problem is happening: in my new project created using my new BSP, if I change a pin behaviour in configuration.xml and I press the "Generate Project content" button, the file pin_cfg.c does not reflect this change. I deleted it and confirmed it is regenerated the same as if I didn't change configuration.xml. For example, in my BSP, pin P000 is defined as an input with IRQ6_DS#. I open configuration.xml and, inside the Synergy Configuration, I change it to Analog Mode (ADC0_AN00). I delete pin_cfg.c and I press the "Generate Project content" button. Then I inspect the newly created pin_cfg.c and I find: const ioport_pin_cfg_t g_bsp_pin_cfg_data[] = { { .pin = IOPORT_PORT_00_PIN_00, .pin_cfg = (IOPORT_CFG_IRQ_ENABLE | IOPORT_CFG_PORT_DIRECTION_INPUT), }, ... Just as it is defined in the base BSP used when I created the project, ignoring my configuration.xml changes that, by the way, keeps correctly changed. Is there any option to stuck the pin configuration of a project to its original BSP no matter what we do to configuration.xml or is it a malfunctioning of my IDE? I'm using e2 studio Version: 5.3.1.002 and SSP 1.2.0. Regards
↧