TOP Contributors

  1. MIKROE (2763 codes)
  2. Alcides Ramos (374 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (118 codes)
  5. Bugz Bensce (93 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (139279 times)
  2. FAT32 Library (71776 times)
  3. Network Ethernet Library (57136 times)
  4. USB Device Library (47436 times)
  5. Network WiFi Library (43101 times)
  6. FT800 Library (42410 times)
  7. GSM click (29835 times)
  8. mikroSDK (28111 times)
  9. PID Library (26887 times)
  10. microSD click (26201 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
Project

Tool: RomSizes

Rating:

10

Author: dany

Last Updated: 2018-03-02

Package Version: 5.2.0.0

Category: Other Codes

Downloaded: 1063 times

Followed by: 1 user

License: MIT license  

This tool shows the romsize of all units of a project together with rom-size details of a selected unit.

For mP, mC and mB for PIC, dsPIC and PIC32.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Tool: RomSizes" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Tool: RomSizes" changes.

Do you want to report abuse regarding "Tool: RomSizes".

  • Information
  • Comments (0)

Project Blog

For mP, mC and mB for PIC, dsPIC and PIC32.

This tool shows the romsize of all units of a project together with rom-size details of a selected unit.

IMPORTANT:
- Be sure that "Include Source Lines in the Output Files, Include ROM Constants and Generate Listfile, include debug info" is checked in menu Tools -> Options -> Output -> OutputSetting.

- The tool is to be started up from within the IDE, it can not be used stand alone.

- Compile the project before tool usage.

More Details...

Screenshot

Screenshot

Screenshot

View full image
Tool settings in the IDE (Options-Tools)

Tool settings in the IDE (Options-Tools)

Tool settings in the IDE (Options-Tools)

View full image

2016-06-17: version 4.9: for the P24/P30/P33 Pic's: corrected the rom sizes (given by the compiler) to rom sizes in bytes, see http://www.mikroe.com/forum/viewtopic.php?f=107&t=33036&hilit=romsize.  

 

---------------------------------------------------------------------------------------------------------------------------------------------
Version 5.0
: added the address of the ROM item.

---------------------------------------------------------------------------------------------------------------------------------------------
Version 5.1
: Corrected an error in the constant sizecalculation for PIC24-dsPic30/33. --------------------------------------------------------------------------------------------------------------------------------------------
Decided to go back to version 5.0: this version shows the actual rom size in bytes used by constants (= 1.5 times bigger that the declaration in mP/mB) for OIC24 and P30/33. For these types of MCU's constants use only 2 bytes per 2 addresses, where 3 bytes per 2 addresses are available.

------------------------------------------------------------------------------------------------------------------------------------------

Version 5.1: Sorting on size of the modulelist corrected.

Version 5.3: Addresses > $FFFF are sorted correctly now.

ALSO FROM THIS AUTHOR

Tool: PIC uart to USB interface

0

Converts PIC level Uart signals to USB in both directions. This project is meant for use with PC's that do not have an RS232 interface any more. It makes it possible to handle the pic uart signals with a PC without an RS232 interface.

[Learn More]

Utilities

26

Several utility libraries: - String Utilities, - SDMMC Utilities, - Bit Utilities, - (standard) Pascal Funtions, - Assert functions, - UartUtils, - Button utilities. - CRC routines

[Learn More]

FRAM Click used without development board

0

The example shows how to use the FRAM click board without a development board. It is executed with a mini32 board instead.

[Learn More]