X-са че е смотан си е смотан, но компилатора си е GCC

За сега ще го карам с volatile пред всяка променлива..

За да добавят няколко прагми и библиотеки, така че ползвателите със засилка от PIC-чета да се чустват по-удобно.

Абе на чупена архитектура като PIC (то това си има и предимства де) да се направи C компилатор си е направо геройство, особенно добре оптимизиращ - иска си сериозна инвестиция за да се хване някой да го прави за без пари

In response to the first entry in this thread. The address shown for findmediaId (r2684354680 (CPU)) is the result of a known bug which affects MPLAB X v3.05. The cause was identified during the v3.10 development cycle and has been fixed.

We do apologize for the inconvenience.

Summary:

It is apparent that the debugger has store the value for findmediaId in one of the CPU working registers in this case. Unfortunately, the bug results in a misinterpretation of way the compiler stores the register info. In this case I am fairly certain that the debugger is adding the value of the stack pointer or frame pointer register to the actual CPU register offset value where the true value is stored. In other words findmediaId is being treated like an auto variable that is offset some number of bytes from the frame pointer base.

You should be able to derive the correct CPU register offset by subtracting the value stored in CPU r30 (frame pointer). Open the PIC memory view for the CPU register window. If compiler optimization is in use, you may need to use the value stored in r29 (stack pointer) since the frame pointer may be omitted. At any rate, the remainder of subtracting the fp or sp value from 2684354680 should be a small value like 2, 3, 4 etc which would relate to CPU register r02, r03 or r04 in this case. One of those working registers should hold the value of findmediaId at the PC address indicated in this debug context.