From c37db738d670ad5fea1a59da4f1a2f1b8a9261f8 Mon Sep 17 00:00:00 2001 From: Xevion Date: Sun, 17 Jul 2022 14:37:19 -0500 Subject: [PATCH] Add preview description & conclusion --- ...022-07-16-restricted-memory-and-data-framing-tricks.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/_posts/2022-07-16-restricted-memory-and-data-framing-tricks.md b/_posts/2022-07-16-restricted-memory-and-data-framing-tricks.md index eb580e1..ed887ab 100644 --- a/_posts/2022-07-16-restricted-memory-and-data-framing-tricks.md +++ b/_posts/2022-07-16-restricted-memory-and-data-framing-tricks.md @@ -4,7 +4,7 @@ title: Restricted Memory & Data Framing Tricks date: 2022-07-16 13:51:00 -0500 tags: c memory embedded ti msp430 union excerpt_separator: -_preview_description: +_preview_description: Tips and tricks I learned about handling restricted memory while working on microcontrollers at my first internship --- Working on microcontrollers is a far cry from the essentially unlimited memory and floating point operations available @@ -195,6 +195,12 @@ void ReverseEndianness(struct AddressedSingleBlockWrite asbw) { } ``` +### Conclusion + +Working in a restricted memory space is not that hard once you get used to the lack of normal functions such as `malloc` +and `printf`, but balancing performance, power consumption, memory allocation and code quality gets harder the more +complex your program gets. + [iso15693-diagram]: /assets/img/iso15693_diagram.png [iso15693-diagram-edn]: /assets/iso15693_diagram.edn [sloa141]: http://www.ti.com/lit/an/sloa141/sloa141.pdf \ No newline at end of file