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.
-c, --comport=port Specify the communication port to be used.
(Default is 0)
0->COM1 / ttyS0
1->COM2 / ttyS1
etc.
-P, --password=file Specify a file with the interrupt vectors that
are used as password. This can be any file that
has previously been used to program the device.
(e.g. -P INT_VECT.TXT).
-f, --framesize=num Max. number of data bytes within one transmitted
frame (16 to 240 in steps of 16) (e.g. -f 240).
-m, --erasecycles=num Number of mass erase cycles (default is 1). Some
old F149 devices need additional erase cycles.
On newer devices it is no longer needed. (e.g. for
an old F149: -m20)
-U, --unpatched Do not download the BSL patch, even when it is
needed. This is used when a program is downloaded
into RAM and executed from there (and where flash
programming is not needed.)
-D, --debug Increase level of debug messages. This won't be
very useful for the average user...
-I, --intelhex Force fileformat to IntelHex
-T, --titext Force fileformat to be TIText
-N, --notimeout Don't use timeout on serial port (use with care)
-B, --bsl=bsl.txt Load and use new BSL from the TI Text file
-S, --speed=baud Reconfigure speed, only possible with newer
MSP403-BSL versions (>1.5, read slaa089a.pdf for
details). If the --bsl option is not used, an
internal BSL replacement will be loaded.
Needs a target with at least 2kB RAM!
Possible values are 9600, 19200, 38400
(default 9600)
-1, --f1x Specify CPU family, in case autodetect fails
-4, --f4x Specify CPU family, in case autodetect fails
--F1x and --f2x are only needed when the "change
baudrate" feature is used and the autodetect feature
fails. If the device ID that is uploaded is known,
it
has precedence to the command line option.
--invert-reset Invert signal on RST pin (used for some BSL
hardware)
--invert-test Invert signal on TEST/TCK pin (used for some BSL
hardware)
--swap-reset-test Swap the RST and TEST pins (used for some BSL
hardware)
--telos-latch Special twiddle in BSL reset for Telos hardware
--telos-i2c DTR/RTS map via an I2C switch to TCK/RST in Telos
Rev.B
--telos Implies options --invert-reset, --invert-test,
--swap-reset-test, and --telos-latch
--telosb Implies options --swap-reset-test, --telos-i2c,
--no-BSL-download, and --speed=38400
--tmote Identical operation to --telosb
--no-BSL-download Do not download replacement BSL (disable automatic)
--force-BSL-download Download replacement BSL even if not needed (the one
in the device would have the required features)
--slow Add delays when operating the conrol pins. Useful if
the pins/circuit has high capacitance.
Program Flow Specifiers:
-e, --masserase Mass Erase (clear all flash memory)
-E, --erasecheck Erase Check by file
-p, --program Program file
-v, --verify Verify by file
The order of the above options matters! The table is ordered by normal
execution order. For the options "Epv" a file must be specified.
Program flow specifiers default to "pvr" if a file is given.
Don't forget to specify "e" or "eE" when programming flash!
Data retreiving:
-u, --upload=addr Upload a datablock (see also: -s).
-s, --size=num Size of the data block do upload. (Default is 2)
-x, --hex Show a hexadecimal display of the uploaded data.
(Default)
-b, --bin Get binary uploaded data. This can be used
to redirect the output into a file.
Do before exit:
-g, --go=address Start programm execution at specified address.
This implies option --wait.
-r, --reset Reset connected MSP430. Starts application.
This is a normal device reset and will start
the programm that is specified in the reset
vector. (see also -g)
-w, --wait Wait for <ENTER> before closing serial port.
If it says "NAK received" it's probably because you specified no or a
wrong password.
make: *** [program] Error 2
I dont know why it is displaying usage help.
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.
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.
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
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
