TOP Contributors

  1. MIKROE (2650 codes)
  2. Alcides Ramos (350 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (112 codes)
  5. Chisanga Mumba (90 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 (136550 times)
  2. FAT32 Library (69743 times)
  3. Network Ethernet Library (55848 times)
  4. USB Device Library (46186 times)
  5. Network WiFi Library (41806 times)
  6. FT800 Library (40997 times)
  7. GSM click (28926 times)
  8. PID Library (26385 times)
  9. mikroSDK (26288 times)
  10. microSD click (25301 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: Record Member alignment for PIC24/dsPIC and PIC32

Rating:

1

Author: dany

Last Updated: 2021-06-13

Package Version: 1.0.0.0

Example: 1.0.0.0

Category: Internal MCU modules

Downloaded: 132 times

Not followed.

License: MIT license  

Describes how record members are stored internally in their records, and what problems to expect if that is not taken into account.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Article: Record Member alignment for PIC24/dsPIC and PIC32" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Article: Record Member alignment for PIC24/dsPIC and PIC32" changes.

Do you want to report abuse regarding "Article: Record Member alignment for PIC24/dsPIC and PIC32".

  • Information
  • Comments (2)
DOWNLOAD LINK RELATED COMPILER CONTAINS
Other Compiler
  • lib
  • src
  • exa
  • hlp
  • hex
  • sch
  • pcb
  • doc

Example Blog

A while ago I ran into a problem related to variable alignment. I tried to read in the data of a record transmitted via Uart by a PIC18 into a PIC32. It went wrong because the internal structure of the record was different between the two PIC families.

Apparently also inside a variable alignment is taken into account.

In this article some observations and possible problems regarding this issue.

2021-06-13: Added another example: the Bootinfo used by the mE bootloaders to send information about the PIC to the PC USB HID bootloader tool.

 

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: Bootloader HOST (windows) for PIC

1

This is (for a change) not a bootloader firmware (the bootloader part present in the PIC), but a bootloader Host for control of the PIC bootloader. It is compatible with the bootloader firmwares from mikroElektronika, and is capable of handling all PIC types. Original development: Joop Beunders.

[Learn More]

Tool: PIC Clear project

5

This tool enables you, in case of troubles, to delete the derived files (*.mcl etc...) in the project directories and the "Defs" directory. It also enables you to edit/check the .mpppi (project) file. For: mP for PIC, dsPIC and PIC32.

[Learn More]