Thanks I updated and the bug seems gone now.
Small suggestion for your page: You may add a note, that tinyos should not be
installed via apt-get after updating, because when you do that, you'll get the
old msp430 version again because of the dependencies. So after installing
msp430-46 according to your documentation (this will delete tinyos if you had
it installed via apt-get before) you have to manually extract tinyos-2.1.2 to
it's previously installed location (usually /opt/tinyos-2.1.2).
________________________________
Von: Eric Decker <[email protected]>
An: "[email protected]" <[email protected]>
CC: Martin Kjeldsen <[email protected]>; "[email protected]"
<[email protected]>
Gesendet: 12:19 Freitag, 5.Juli 2013
Betreff: Re: [Tinyos-help] Strange memory bugs
4.6.1 has known bugs.
following the instructions at http://tinyprod.net/repos/debian/
On Fri, Jul 5, 2013 at 1:24 AM, [email protected]
<[email protected]> wrote:
The application in which the bug occurs is about 10k LOC, so posting it
wouldn't help here. Unfortunately I am not able to reproduce it in a smaller
sample application.
>
>
>I am compiling for the telosb platform using the msp430 toolchain (using
>Ubuntu 11.10 in a VM).
>
>
>During compilation I always get "WARNING: Minimum recommended msp430-gcc
>version for this TinyOS release is 4.6.3!!!". I currently have gcc 4.6.1 but I
>don't know how to update.
>If I try "sudo apt-get upgrade msp430-gcc" I still have 4.6.1 afterwards and
>tos-bsl is removed, so I cannot install on motes anymore.
>
>
>May this warning be the trigger of the problem?
>
>
>
>________________________________
> Von: Eric Decker <[email protected]>
>An: "[email protected]" <[email protected]>
>CC: "[email protected]"
><[email protected]>
>Gesendet: 18:20 Donnerstag, 4.Juli 2013
>Betreff: Re: [Tinyos-help] Strange memory bugs
>
>
>
>this has nothing to do with tinyOS or nesC.
>
>
>Something going on with the toolchain.
>
>
>Which you don't specify. What cpu are you compiling for, what toolchain, and
>what version?
>
>
>
>On Thu, Jul 4, 2013 at 5:42 AM, [email protected]
><[email protected]> wrote:
>
>Hi all,
>>
>>
>>I am experiencing some strange memory bugs regarding arrays in my TinyOS
>>application. Here is an example:
>>
>>
>>uint32_t arr[6][3]; //global var
>>
>>
>>void setter()
>>{
>>arr[1][2] = 34;
>>}
>>
>>
>>uint32_t getterA()
>>{
>>return arr[1][2];//34
>>}
>>uint32_t getterB()
>>{ uint8_t a = 1; uint8_t b = 2;
>>return arr[a][b];//0
>>}
>>uint32_t getterC()
>>{ uint8_t a = 1; uint8_t b = 2; uint32_t *temp;
>>temp = &(arr[a][b]);
>>return *temp;//34
>>}
>>bool adrEqual()
>>
>>{ uint8_t a = 1; uint8_t b = 2;
>>return &(arr[1][2]) == &(arr[a][b]);//true
>>}
>>
>>
>>So when I call setter() and then one of the getters, I get the given values.
>>The problem is of course getterB. I currently fixed this by using the
>>workaround of getterC, but I would prefer fixing the problem and not just the
>>symptoms. So if anyone has an idea what may cause this strange behavior I
>>would be very thankful if he would share this with me.
>>
>>
>>Best regards
>>_______________________________________________
>>Tinyos-help mailing list
>>[email protected]
>>https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>
>
>
>--
>Eric B. Decker
>Senior (over 50 :-) Researcher
>
>
>
>
--
Eric B. Decker
Senior (over 50 :-) Researcher_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
