Hi,
I'd like to call the sdcc compiler from an other program, in Windows. Is
there any way to get back the compile status, compile error? Getting the the
status of compiling (0 or 1 for example, the compiling successfull or not),
and getting the error line no, in case of syntax error.
Thanks
Is this program correct? This should work? (blinking led)
#include "pic16f84.h"
void main()
{
TRISB = 0;
for (;;)
{
PORTB = 0;
PORTB = 1;
}
}
-
Check out the new SourceForge.net Marketplace.
The startup code is the pic asm version of this routine?
sdcc/device/lib/libsdcc/idata.c
void _sdcc_gsinit_startup(void)
For PIC14 (for example p16f84)
Thanks
-
Check out the new SourceForge.net Marketplace.
It's the best pl
The real program will start at 0xCD ?
;
STARTUP code
00 nop nop
pagesel __sdcc_gsinit_startup
01 2805 goto
I tried to simulate (PICSim IDE, Oshonsoft) the hex file, but I got
"Hardware stack overflow"
#include "pic16f84.h"
void main()
{
TRISB = 0;
for (;;)
{
PORTB = 0;
PORTB = 1;
}
}
" \sdcc\bin\sdcc.exe" --vc -mpic14 -p16f84 blinkled.c
Thanks
wrote:
>
>
> Get Started wrote:
> > I tried to simulate (PICSim IDE, Oshonsoft) the hex file, but I got
> > "Hardware stack overflow"
>
> There was a similar report recently stating the same problem. Can you
> track it down more precisely? Can you single-step
On 6/8/08, Raphael Neider <[EMAIL PROTECTED]> wrote:
>
>> Instructions counter: 94
>> Clock cycles counter: 484
>> Last instruction: call 0xAC
>
> OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
> by selecting the correct PIC (16f84) rather than using the simulator's
> defau
I tested it with p16f84 in PIC Simulator IDE previously...
On 6/9/08, Raphael Neider <[EMAIL PROTECTED]> wrote:
>
>>> OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
>>> by selecting the correct PIC (16f84) rather than using the simulator's
>>> default (16f877), which mes
