• Please tell me how to check the ROM size for each file.
    • If you check [Do not generate separate segment per function] in the compiler option settings (Properties> Settings> Tool Settings tab Compiler> Code Generation) of LEXIDE-U16, you can prevent the segment from being divided into function units. From this, you can check the ROM consumption of each file in the map file.
      At this time, the segment name for the function is $$NCODfilename or $$FCODfilename, and the segment name of the constant data is $$NTABfilename or $$FTABfilename, so check the map file.

      However, if you set this option, the code size may increase because unreferenced functions and constant data are also included in the segments of the file. Also, please understand that the ROM consumption is not an accurate value because the HEX data for each file may change slightly.

      Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

    • Produkte: General-purpose MCUs (16bit) , Speech Playback MCUs (8bit)