Searching \ for '[PIC] "in segment BANK0 (error)"' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/memory.htm?key=bank
Search entire site for: '"in segment BANK0 (error)"'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] "in segment BANK0 (error)"'
2007\03\23@094424 by microsoftwarecontrol

flavicon
face
part 1 497 bytes content-type:text/plain; (decoded quoted-printable)

: : Can't find 0x5E words for psect rbss_0 in segment BANK0 (error)
: : Can't find 0xC words for psect temp in segment COMBANK (error)
: : Can't find 0x2 words (0x2 withtotal) for psect code_ptr in segment BANK0 (er
ror)



I saw this kind error for 3 days now. Is there some general guidelines to avoid these kind RAM usage error? Any good book?

"0x5E" seems too much. Before, I met much less and easy to solve. But this is terrible!





part 2 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

2007\03\23@102139 by Mauricio Jancic

picon face
It indicates that there is not enough room for the registers that you
defined. Perhaps you have an array or something like that.
The first step would be to check if everything is well defined. If it is,
you may want to check wich variables can be made local to functions and
volatile (default) instead of static.
Then start putting some of the variables on another bank, using the bank1,
bank2, etc modifiers.

Mauricio Jancic
Janso Desarrollos
Microchip Certified Consultant
http://www.janso.com.ar
spam_OUTinfoTakeThisOuTspamjanso.com.ar
(54) 11-4502-2983


> {Original Message removed}

2007\03\23@102407 by Michael Rigby-Jones

picon face
part 1 1981 bytes content-type:text/plain; (unknown type 8bit not decoded)



{Quote hidden}

That error does not mean that you need an extra 0x5E words of RAM, it simply means that the rbss_0 psect is 0x5E words and the linker was unable to find an unused, contiguous block of RAM within the required bank of that size.  In fact it may be that you only need to free up one or two words to make it fit.  Simply move some of your global variables into one of the other banks using the bank1, bank2 or bank3 modifiers (dpending on how many banks your PIC has).

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================



part 2 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

2007\03\23@130051 by Nigel Duckworth

picon face
part 1 703 bytes content-type:text/plain; charset=GB2312 (decoded 7bit)

Which PIC are you compiling for and did this happen when you added a
little more code at around 50% memory usage?



microsoftwarecontrol wrote:
{Quote hidden}


part 2 35 bytes content-type:text/plain; charset="us-ascii"
(decoded 7bit)

2007\03\23@134603 by microsoftwarecontrol

flavicon
face
part 1 1241 bytes content-type:text/plain; (decoded 7bit)

16f876a and 16c72a.

same error and it's related to RAM usage.


{Original Message removed}

2007\03\23@153738 by Nigel Duckworth

picon face
part 1 1848 bytes content-type:text/plain; charset=GB2312 (decoded 7bit)

I had a similar error with the Hi-Tech PICC-18 compiler;

'can't find 0x4040 words (0x4040 withtotal) for psect "text" in segment
"CODE"

... which turned out to be a silicon bug.

It's not necessarily a RAM problem, have you read the Hi-Tech FAQ?

http://www.htsoft.com/support/faqs.php#faq83

Nigel


microsoftwarecontrol wrote:
>  
> 16f876a and 16c72a.
>
> same error and it's related to RAM usage.
>
>
> {Original Message removed}

2007\03\23@155910 by John Temples

flavicon
face
On Fri, 23 Mar 2007, Nigel Duckworth wrote:

> It's not necessarily a RAM problem, have you read the Hi-Tech FAQ?

It is a RAM problem when the error references BANK0.


> microsoftwarecontrol wrote:
>>
>> 16f876a and 16c72a.
>>
>> same error and it's related to RAM usage.
>>
>>
>> {Original Message removed}

More... (looser matching)
- Last day of these posts
- In 2007 , 2008 only
- Today
- New search...