I need to use the RA0E1 IICA_SLAVE.With e² studio 2024-04 and FSP 5.2.0 it was not possible to add it with "New Stack", only IICA_MASTER could be added.
With e² studio 2024-04 and FSP 5.3.0 it is possible to add it with "New Stack";in the Stacks/Properties Tab SCLA and SDAA Pin can be assigned to a port numberbut after changing to the "Pins/Pin Function" Tab there in the Section Peripherals/IICA/IICA0 the Operation Mode is disabled and cannot be Enabled !?
With e² studio 2024-04 and FSP 5.4.0 it is possible to add it with "New Stack";in the Stacks/Properties Tab SCLA and SDAA Pin can be assigned to a port numberbut after changing to the "Pins/Pin Function" Tab there the Section Peripherals/IICA/IICA0 is completely missing !?
The problem is reproducible on another PC of a collegue.Does anybody know if there is a solution to this behaviour ?
Hi Harley ,
Thanks for your prompt response.
is there any reason why i cannot configure the slave address below 0x08 ? we are looking for backward compatibility with our old design (where master is communicating with slave address 0x01)
Regards,
Anil
As far as I can see only 0x00 to 0x02 are reserved addresses, I don't know if and why Renesas implemented it with that restriction (0x08 in properties, which results in physical address of 0x10), maybe a someone from Renesas can answer that ... ?I also never received an answer from them to my question above about what the duty cycle setting is good for with an I2C slave ...
Hi Anil,
what is your current issue, actually? Neither in the FSP documentation, nor in the FSP stack I can see any rectrictions. You should be able to use slave addresses down to 0x00.
Cheers,
Ralf
Hi RalfG,
The main issue is with slave address, i cannot set it to 0x01 .
i was using FSP5.3.0 then later following this thread i upgraded to 5.4.0
firstly i couldn't see IICA under list of peripheral to configure the pins P212 & P213 , they are listed as disabled under pin configuration. little bit of ambiguity here whether they are configured as I/o by default or as peripheral
if i enable "general calling" in the stack properties i could see the isr_callback triggered during debugging but not when i disabled and waiting through specific configured slave address.
OK, now I see your issue:
This error message is not caused by a hardware or FSP stack restriction. It is simply a notification of a compliance issue wrt the I²C specs. The specs reserve 7bit addresses below 0x08 and above 0x77 for special use (e.g. address 0x00 for general calls or 0x78 for 10bit addressing). See below a comprehensive list:
On your local bus, you do not need to adhere to this, you can do whatever you want as long a your local bus participants can deal with it.
The error message is generated right out of the configuration properties tab. You can live with it, as proper code is generated anyway (I have not checked, though).
A better solution is to change Parameter Checking to default(BSP) or disabled. Then the message diminishes.
Hi Ralf,
I've tried changing the "parameter checking " to disabled and kept the slave address ' 0x01 ' but no luck , error still remains and wouldn't allow me to run in debug mode . is there anything i could do to clear the error .
thank you.
A N