By default Ubuntu hides files starting by "." Just press ctrl + h to see them.
About the BSL work, as Eric said, you need to go through the script and see how
it works.
Regards,
Eric Decker <cire...@gmail.com> wrote:
>On Sun, Jan 22, 2012 at 9:57 PM, dwaraka nath <dwaraka.tul...@gmail.com>wrote:
>
>> Hi Eric,
>>
>> After following your suggestion, I followed Z1 platform and I made for a
>> new platform "mymote" . when i compile Blink app it is compiling properly.
>> When I try to Install using BSL. it is not initializing.
>>
>> the message i got is as follows..
>>
>> dwaraka@ubuntu:/opt/tinyos/apps/Blink$ make mymote install
>> mkdir -p build/mymote
>> compiling BlinkAppC to a mymote binary
>> ncc -o build/mymote/main.exe -Os -fnesc-separator=__ -Wall -Wshadow
>> -Wnesc-all -target=mymote -fnesc-cfile=build/mymote/app.c -board=
>> -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\"
>> -DIDENT_USERNAME=\"dwaraka\" -DIDENT_HOSTNAME=\"ubuntu\"
>> -DIDENT_USERHASH=0xb9dea24aL -DIDENT_TIMESTAMP=0x4f1ce795L
>> -DIDENT_UIDHASH=0xd028fdffL BlinkAppC.nc -lm
>> compiled BlinkAppC to build/mymote/main.exe
>> 2200 bytes in ROM
>> 56 bytes in RAM
>> msp430-objcopy --output-target=ihex build/mymote/main.exe
>> build/mymote/main.ihex
>> writing TOS image
>> cp build/mymote/main.ihex build/mymote/main.ihex.out
>> found mote on /dev/ttyUSB0 (using bsl,auto)
>> installing mymote binary using bsl
>> tos-bsl --mymote -c /dev/ttyUSB0 -r -e -I -p build/mymote/main.ihex.out
>> MSP430 Bootstrap Loader Version: 1.39-telos-8
>>
>> USAGE: /usr/bin/tos-bsl [options] [file]
>> Version: 1.39-telos-8
>>
>> If "-" is specified as file the data is read from the stdinput.
>> A file ending with ".txt" is considered to be in TIText format,
>> '.a43' and '.hex' as IntelHex and all other filenames are
>> considered as ELF files.
>>
>> General options:
>> -h, --help Show this help screen.
>>
>>
>...
>
>
>>
>> I dont know why it is displaying usage help.
>>
>
>It is complaining because tos-bsl doesn't understand "--mymote".
>
>The Z1 folks had to teach tos-bsl about differences between the telosb and
>the z1. In other words they had to modify tos-bsl so that it would
>properly interface to the Z1 BSL hardware.
>
>Expecting it to just work out of the box for a new platform is not
>reasonable unless of course your bsl h/w is purposely the same as the
>telosb or z1.
>
>Either way, one needs to understand how the bsl works and how it is invoked
>from the usb side. You need to figure this out for your new mote to play
>when in bsl mode.
>
>And none of this is properly documented. TI documents how to deal with
>BSL and the h/w signals that need to be wiggled. But how this is done on
>say the telosb or Z1 isn't documented and the linkage from the USB side to
>the BSL signaling isn't documented.
>
>
>
>> I have gone through tos-bsl in /usr/bin/tos-bsl and I found patch for F1x
>> and F4x and the series of processors belonging to those families. I couldnt
>> find F2x and the related processors.
>>
>
>Look at the changes that Antonio brought in. Try r5693. You probably
>aren't on the trunk. Is my guess. Where did you get your source from?
> I thought you are on the trunk. If you are on the trunk you should see
>something like:
>
>#cpu types for "change baudrate"
> #use strings as ID so that they can be used in outputs too
> F1x = "F1x family"
>+F2x = "F2x family"
> F4x = "F4x family"
>
> #known device list
> deviceids = {
> 0xf149: F1x,
>- 0xf16c: F1x, #for telosb
>+ 0xf16c: F1x, #for GoodFET10 to '20
> 0xf112: F1x,
> 0xf413: F4x,
> 0xf123: F1x,
> 0xf449: F4x,
> 0x1232: F1x,
>+ 0xf26f: F2x, #for GoodFET20
>+ 0xf227: F2x, #for GoodFET30
>+}
>
>This is from the file: tools/platforms/msp430/pybsl/tos-bsl.in
>
>
>
>>
>> More over i'm able to see ".platform" file in windows only and not in
>> Ubuntu. Even if i see the same folder contains ".platform" from Ubuntu.
>>
>
>I have no idea what you are actually trying say there. I'm not parsing
>your English. What .platform file are you talking about? And what state
>is your tree in on Windows vs. Ubuntu?
>
>Is there some reason why your changes on the Windows side should have
>propagated over to the Ubuntu side?
>
>eric
>
>
>
>>
>> On Sat, Jan 14, 2012 at 9:00 AM, Eric Decker <cire...@gmail.com> wrote:
>>
>>>
>>>
>>> On Fri, Jan 13, 2012 at 5:10 AM, dwaraka nath
>>> <dwaraka.tul...@gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>> I have motes with MSP430f2618+CC2520 and MSP430f1611+CC2520. is it
>>>>>> possible to reduce the existing Applications (like PppRouter) so that
>>>>>> they
>>>>>> can fit on 8k RAM of 2618 ???
>>>>>>
>>>>>
>>>>> Why do you think you are overflowing the 8K of RAM?
>>>>>
>>>>
>>>> When I compile PppRouter Application it is occupying around 48kB of ROM
>>>> and 9.5kB of RAM which obviously wont fit into 2618 even i program it
>>>> through my FET-UIF.
>>>>
>>>
>>> yeah that won't fit. you'll have to do some work to figure out where
>>> all the RAM is being assigned and then do some work to trim it.
>>>
>>>
>>>
>>>>
>>>>>
>>>> You should look at what the z1 folks did. Their bsl seems to work.
>>>>> But I don't know what the differences are. I do know they had to tweak
>>>>> things a bit. They did bring those changes into the trunk.
>>>>>
>>>>
>>>> Should I check the compilation of the Applications for Z1 mote??
>>>>
>>>
>>> yes. And see Antonio's response to this email.
>>>
>>>
>>>
>>>> How can I configure CC2520 to MSP430f1611 as for MSP430f1611+CC2420 in
>>>>>> TelosB.
>>>>>>
>>>>>
>>> A couple of things you'll need to do....
>>>
>>> 1) You will need to look at the interfaces/abstraction barriers that are
>>> provided by the 2420 stack and the 2520 stack. They should be the same
>>> at a high enough level.
>>>
>>> 2) You will need to figure out how to change the search paths. This is
>>> accomplished via the .platform file.
>>>
>>> The TelosB platform is defined by tos/platforms/telosb and
>>> tos/platforms/telosb/.platform defines the search order for building
>>> applications for the telosb platform.
>>>
>>> tos/platforms/z1 defines the Z1 platform.
>>>
>>> So you will need to create a new platform with a modified .platform file
>>> that causes the cc2520 code to be pulled in rather than the cc2420 code.
>>>
>>> You will need to figure this out yourself. I don't have time to teach
>>> it to you.
>>>
>>> Try starting with: http://docs.tinyos.net/tinywiki/index.php/Platforms
>>>
>>>
>>>
>>>>
>>>>> I don't know what that means... Want to try asking it again?
>>>>>
>>>>
>>>> As TelosB is linked with 2420. Is it possible to link my 1611 with
>>>> CC2520 as support has come for 2520 If so pls let me know the way i can
>>>> configure TinyOS with my hardware ( 1611+2520)
>>>>
>>>
>>> See above.
>>>
>>>
>>>>
>>>>
>>>>>
>>>>>
>>
>>
>> --
>> Tulasi Dwarakanath.V
>>
>
>
>
>--
>Eric B. Decker
>Senior (over 50 :-) Researcher
>
>_______________________________________________
>Tinyos-help mailing list
>Tinyos-help@millennium.berkeley.edu
>https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
