Search found 8 matches

I get trouble in using itoa in multiple compile unit.
Here's my code:

#include "18F46K22.H"
#include "stdlib.h"

void main(){
char buf[] = " ...

From software engineering perspective, i'd like to separate my code into several different module, hence the source code conflict could be avoided when collaborate with my partner and also code is of ...

Interesting discovery:

If I compiled in a single compilation unit, the result is just what I expected:

a = 1, b=11
a = 2, b=12
a = 3, b=13
a = 4, b=14
a = 5, b=15
a = 6, b=16

However, ...

Hi there,
I found a easy way to reproduce the issue:

const BYTE a[] = {1,2,3,4,5,6};
const BYTE b[] = {11, 12,13,14,15,16};

void main(){
s ...

No, i know the pointer to const issue/limitation.
My usage is almost the same as below code, no pointer is involved.

const BYTE b[] = {1,2,3,4};
void foo()
{
...

Two const arrays locate in separated rom spaces, which is expected, if #device const=rom is not defined in header.
Hence I think the abnormal behavior is caused by this directive.

Anyway, the purp ...

Thanks for replying, Ttelmah

The multiple compilation units work fine in my project except this rom space overlap issue. I checked the mcu.zip you mentioned but I didn't find anything about how to ...

compiler: 5.025
Hardware: PIC18F46K22
IDE: MPLAB X

It is probably a compiler issue, but i'm not sure. Hence i post it and see who else encounter the same issue.

The symptom is when multiple co ...