You're basicly asking for a compiler update, which is a painful and time
consuming task. I'm responsible for the avr toolchain, but as the name
suggests, it's just a tool, and I rather work on tinyos softwares than
tools. I only do this, because nobody else does.
The gcc 4.8 based beta toolchain will be released in the next couple of
weeks at least for dpkg based linux and cygwin.
Sorry for your incovinience.

Andris


On Thu, May 22, 2014 at 11:46 PM, Roadstar Runner <[email protected]>
wrote:

>
> I honestly think TinyOS is dying! The activity on the forum is almost down
> to a trickle. It takes forever to get problems fixed ( if they do ever get
> fixed) .
> I have been stuck for more than a week trying to get the avr-studio-debug
> flag to work with even a NseC program that is of respectable size (that
> includes the radio stack) on the IRIS platform .
> The solution seems to be to upgrade the gcc toolchain, though  updating
> the toolchain to work with TinyOS is almost a nightmare.
> I stumbled upon a few rpms from Janos, but they dont install.
> I seriously think new projects should think twice before using TinyOS in
> their products
>
>
> On Thu, Apr 10, 2014 at 1:48 PM, Philip Levis <[email protected]> wrote:
>
>> This seems to be a basic avr-gcc problem:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19087
>>
>> It seems the general solution people are proposing involves rebuilding
>> the compiler/tool chain so that dwarf debugging addresses are 2 bytes
>> rather than 4. I am wondering whether newer avr-gcc releases solve this
>> problem.
>>
>> Phil
>>
>>
>>
>>
>> On Apr 10, 2014, at 10:30 AM, Roadstar Runner <[email protected]>
>> wrote:
>>
>> > Phil,
>> > Thanks once again.
>> > Is there an easy way for me to find a fix/workaround ?
>> > Lewis
>> >
>> >
>> >
>> >
>> > On Thu, Apr 10, 2014 at 12:13 PM, Philip Levis <[email protected]>
>> wrote:
>> > (responded to this unicast, thought I would put it here too)
>> >
>> > It looks like the avr-studio-debug flag doesn't support code sizes
>> greater than 65,535 bytes. I'm not exactly sure why.
>> >
>> > Phil
>> >
>> >
>> >
>> >
>> > On Apr 8, 2014, at 3:00 PM, Roadstar Runner <[email protected]>
>> wrote:
>> >
>> > >
>> > > I have been compiling my program  with the 'avr-studio-debug' flag so
>> that i can use a JTAG to debug my software.
>> > > Recently, even though my program compiles normally without the debug
>> flag, it fails when i use the avr-studio-debug flag. I get a bunch of
>> cryptic error message that reads like this
>> > >
>> > > /tmp/ccEjxlre.s:74677: Error: value of 65568 too large for field of 2
>> bytes at 26349
>> > >
>> > >
>> > > It seems that code i add, even modifying a local variable causes the
>> compilation to fail.
>> > >
>> > > Here is my ROM/RAM size that compiles correctly with the debug flag.
>> > >
>> > > 68796 bytes in ROM
>> > > 614 bytes in RAM
>> > >
>> > > Thanks
>> > >
>> > > _______________________________________________
>> > > Tinyos-help mailing list
>> > > [email protected]
>> > >
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>> >
>> >
>>
>>
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to