# Include error local compile Photon

**URL:** <https://community.particle.io/t/include-error-local-compile-photon/13052>\
**Category:** Firmware\
**Created:** [July 7, 2015, 4:04pm UTC](https://community.particle.io/t/include-error-local-compile-photon/13052 "2015-07-07T16:04:49Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![HardWater](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/hardwater/32/4186_2.png) [@HardWater](https://community.particle.io/u/HardWater)\
**Post date:** [July 8, 2015, 12:32pm UTC](https://community.particle.io/t/include-error-local-compile-photon/13052/8 "2015-07-08T12:32:21Z")

</div>

Hi @peekay123 what you say makes sense to me but it seems to conflict with @mdma comment

> [@Implications of customized system firmware - Photon](https://community.particle.io/t/implications-of-customized-system-firmware-photon/12948/5):
>
> The user code has full access to all the hardware, so there should be no hindrances to doing this.

from this other thread [Implications of customized system firmware - Photon - #8 by HardWater](https://community.particle.io/t/implications-of-customized-system-firmware-photon/12948/8) where similar issues were discussed.

I did a search for the source for dct\_read\_app\_data & dct\_write\_app\_data but cannot find it in the repo only that it is defined as an extern function. I was thinking that maybe there are lower level commands that I need to execute to access the hardware and those commands were accessable.

---

_[View the full topic](https://community.particle.io/t/include-error-local-compile-photon/13052)._