Hi Eric,
I have the same tos-bsl.in file you mentioned.
>
> 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.
>>
>>
>
>> I dont know why it is displaying usage help.
>>
>
> It is complaining because tos-bsl doesn't understand "--mymote".
>
whether i need to add any path. If so where can I ??
>
> 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.
>
when I searched for BSL programming "slau319a.pdf" , I understood that BSL
pins must be connected to USB in order to program through it. My hardware
has the same connections.
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:
>
I updated the trunk now I have the same tos-bsl.in what u said.. Thank
you..
>
> #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
>
what does the GoodFET20 mean here. I have gone through
http://goodfet.sourceforge.net/hardware/goodfet20/ and
http://goodfet.sourceforge.net/hardware/goodfet30/<http://goodfet.sourceforge.net/hardware/goodfet20/>.
I didnt understand whether the Hardware must follow the GoodFET
architecture for bsl programming or I need GoodFET mudule ( like that of
MSP FET430 -UIF ) for emulation ???
Also I dont understand how the Patches ans BSLs for F1x and F4x are added
from the application note slaa089a
I have gone through many third party BSL programmers all described the BSL
programmer like USB to JTAG converter
http://www.flyingcampdesign.com/uploads/3/5/3/8/3538283/10001_msp430_bsl_programmer_schematic.pdf
How Z1 is programmed ???
Using direct USB or any Intermediate tool like MSP FET430-UIF ???
If possible please provide me the architecture of Z1 mote so that I can
compare my hardware with it.
--
Tulasi Dwarakanath.V
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
