I think the problem is here:
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3521376&group_id=599
Don Wooton was writing about when appeared it. I found the same
result, when I started to examine the code. _cinit is an address in
code memory, but the compiled code looks like it handle like a general
purpose register. The BANKSEL macro is used to select a register bank.
But _cinit is not a register in a bank.
MOVLW 0x02
BANKSEL _cinit
ADDWF (_cinit + 0),W
BANKSEL r0x1002
MOVWF r0x1002
CLRF r0x1003
RLF r0x1003,F
BANKSEL _cinit
MOVF (_cinit + 1),W
BANKSEL r0x1003
ADDWF r0x1003,F
2012/6/22 Borut Ražem <[email protected]>:
> On Fri, Jun 22, 2012 at 5:56 PM, Gál Zsolt <[email protected]> wrote:
>>
>> Hello,
>>
>> I realised that my programs doesn't work if I don't use a simple
>> routine to avoid linking the sdcc_gsinit_startup code. It could be
>> problematic for those sdcc users who started to use sdcc for a couple
>> months ago. I am using this simple code for my programs, because the
>> generated code is smaller:
>>
>> void _sdcc_gsinit_startup(void)
>> {
>> __asm pagesel _main __endasm;
>> __asm goto _main __endasm;
>> }
>>
>> It was offered in the mail-list somewhere. Unfortunately I run into
>> this problem time to time, when I start a new project. My first step
>> is driving a LED, which is very simple if everything is working. My
>> brain is very small, so I am alway forgetting to add this simple
>> routine to the program, and the LED isn't working as I expected.
>>
>> I am downloading the source of SDCC from svn every time and do the
>> compiling myself. I was thinking that I am doing something with it,
>> and that is why gsinit doesn't working. Today I downloaded and
>> installed the SDCC 3.2.0 rc1, but the situation is the same. So my
>> program doesn't work if I don't avoid to linking the gsint routine
>> from the library.
>>
>> If I will have more time I will check where the program strugle. I
>> hope on this weekend I will have time for it.
>
>
> Any help is welcome!
>
> If it is really caused by bug ID 3521376
> at http://sourceforge.net/tracker/?func=detail&aid=3521376&group_id=599&atid=100599 it
> would be fine if somebody check in which svn revision the bug appeared and
> which change in sdcc source code caused it. The information in the bug
> report seems inaccurete to me: no pic14 related changes were made in svn
> revision #7080.
>
> Borut
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Sdcc-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>
--
~~~~~~~~~~~~~~~~
http://galzsolt.zzl.org
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
