Hello Team, We are working on adding pre-check support for Renesas RX65N MCU. We are getting the below warnings in the common files used across the Renesas MCUs (M16, SH1 and RX65N).
1. arch/renesas/src/common/up_blocktask.c: passing argument 2 of ‘up_copystate’ discards ‘volatile’ qualifier from pointer target type 2. arch/renesas/src/common/up_releasepending.c: passing argument 2 of ‘up_copystate’ discards ‘volatile’ qualifier from pointer target type 3. arch/renesas/src/common/up_reprioritizertr.c: passing argument 2 of ‘up_copystate’ discards ‘volatile’ qualifier from pointer target type 4. arch/renesas/src/common/up_unblocktask.c: passing argument 2 of ‘up_copystate’ discards ‘volatile’ qualifier from pointer target type 5. arch/renesas/src/common/up_doirq.c: assignment discards ‘volatile’ qualifier from pointer target type 6. arch/renesas/src/common/up_initialize.c: implicit declaration of function ‘up_serialinit’ 7. arch/renesas/src/common/up_usestack.c: assignment makes pointer from integer without a cast 8. net/mld/mld_group.c: label ‘errout_with_sem’ defined but not used The following modifications would resolve the above mentioned warnings. Warnings 1, 2, 3 and 4 mentioned above can be resolved by typecasting the argument 2 of ‘up_copystate’ to the type of the actual parameter while invoking the function as follows: up_copystate(rtcb->xcp.regs, (uint32_t *)up_current_regs); Warning 5 can be resolved similarly by typecasting the variable upon assignment as follows: regs = (uint32_t *)g_current_regs; Warning 6 can be resolved by including the function declaration for up_serialinit() in the header file up_internal.h. Warning 7 can be resolved by typecasting the variable top_of_stack to (void *) as follows: tcb->adj_stack_ptr = (void *)top_of_stack; Warning 8 can be resolved by removing the label 'errout_with_sem' as it is simply defined but not used anywhere in the function. Unless these warnings are cleared, RX65N cannot be added to the pre-check since due to the [-Werror] flag, the build fails. As the above mentioned files are common files to m16 and sh1 architectures also, can you confirm whether the above modifications are okay. Regards, Bhindhiya Raja ________________________________ Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version. ________________________________
