TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 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 (141469 times)
  2. FAT32 Library (74308 times)
  3. Network Ethernet Library (58852 times)
  4. USB Device Library (48918 times)
  5. Network WiFi Library (44679 times)
  6. FT800 Library (44220 times)
  7. GSM click (30933 times)
  8. mikroSDK (29814 times)
  9. PID Library (27414 times)
  10. microSD click (27352 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
Example

Article: Ram corruption reasons in mP and mB

Rating:

5

Author: dany

Last Updated: 2018-08-02

Package Version: 2.0.0.0

Example: 1.0.0.0

Category: Other Codes

Downloaded: 726 times

Not followed.

License: MIT license  

Purpose: Make people aware about the ways of working that can introduce ram corruption
(and of course how to avoid it). In this document the many ways where it goes right are not mentioned, only the danger areas are highlighted.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Article: Ram corruption reasons in mP and mB" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Article: Ram corruption reasons in mP and mB" changes.

Do you want to report abuse regarding "Article: Ram corruption reasons in mP and mB".

  • Information
  • Comments (3)
DOWNLOAD LINK RELATED COMPILER CONTAINS
Other PIC Compilers
  • lib
  • src
  • exa
  • hlp
  • hex
  • sch
  • pcb
  • doc

Example Blog

Purpose of this article: Make people aware about the ways of working that can introduce ram corruption (and of course how to avoid it). In this document the many ways where it goes right are not mentioned, only the danger areas are highlighted.  

The document in .pdf format

Please forward your suggestions or additions via the "comments" tab. The article is most possible not complete. All suggestions are wellcome!


2014-08-12: Added a few items: - no terminating zero in a string - "SizeOf" usage with "external" items.


2014-08-21: Added the mikroBasic examples...


2014-08-26: small addition into the "non terminating a string with zero" part...


2014-12-07 (v2.0): added a nasty one:  passing e.g. a byte as var parameter where a word parameter was expected and assigning a value to it inside the procedure.


2015-06-06: added again a nasty one: using '+' to concatenate a string passed to a function as parameter, see http://www.mikroe.com/forum/viewtopic.php?f=106&t=64658.Thanks Jim Keuneman!


2015-06-09: Updated the document again: added the "StrnCpy" issue and the concat (with +) issue for a var string + a const string.


2015-07-10: Added some "tips" (thanks Acko).

ALSO FROM THIS AUTHOR

USB HID CDC MSD composite device

5

This project uses all the available types of USB devices in the USB_OA library: HID (application echos chars send by the PC to the PC), CDC (application echos chars send by the PC to the PC), MSD (the contents of an SD/MMC card is presented to the PC as an extra drive).

[Learn More]

Tool: Global variable usage

10

Shows, from a selected routine, the following items: - The parameter - The (used) local variables - The unused local variables (eliminated by optimiser) - The used global variables - Called routines For Pic, Pic24 and P32, both mP and mB

[Learn More]

Fat

24

Several libraries for Fat16 and Fat32: - Fat16Dir (findfirst, findnext) (only P18) - Fat16DirLFN (Fat16Dir for long filenames) (only P18) - Fat32_,1 Fat32_2; single and multiple Fat32 device(s) for P18, PIC24, dsPIC and PIC32 - IDE for P18, PIC24 and dsPIC.

[Learn More]