Hi Puru, I'm assuming that your hardware design either corresponds to Mica2 or that you have reflected the changes in the hardware.h file (see Firat's mail).
TinyOS should not refer to components that you haven't linked in. I'm more wondering if there is a wiring problem somewhere. While Blink is a simple program, there is even a simpler program: Null (at least in TinyOS-2). I would use the Null application as a starting point and just enable some LEDs in the booted() function call using either assembly instructions or c-code. Using these low-level instructions ensures that the state of the LEDs get changed even if there is somehow a problem with the TinyOS Led component (you don't even have to link it in). If this works, then you know at least that the basic TinyOS boot sequence works on your hardware. Then you can test the TinyOS Led component. Once this works as well, try the Blink application. Cheers, Urs Puru schrieb: > Hi Urs, > > I wrote a simple program using ICC-AVR, which toggled bits on > port A and which in turn blinked the leds and this hex program > when copied on the platform worked correctly. > infact this hex file copied on the mica2 using uisp also works correctly. > i tried with and without the timer. > note this is not using assembler directives in NesC, but similar > assemble directives with the icc-avr interface. > > am not sure if tinyos is looking for h/w that is not present > on the platform (e.g., flash, radio etc and failing, which i think is > unlikely), > or if i am some wrong settings or smtg else ... > > thanks, > -- puru > > > On 5/29/07, Urs Hunkeler <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Do the LEDs work if you write a simple program in assembler? Can you >> control the LEDs when using assembler directives in NesC code (without >> timer)? If yes, does it also work with timers? >> >> Cheers, >> Urs >> >> >> Puru schrieb: >> > hi all, >> > >> > we are developing a mote-like (mica2-like) device, which currently >> > only has the mcu and minimum cicuitry to get it started >> > (no external flash, no radio yet). >> > >> > the initial idea is to compile apps using tinyos and >> > copy the corresponding ihex files using icc-avr or such >> > onto the new platform. we are facing problems with >> > this procedure, have tried testing the procedure using Blink, >> > as the LED circuitry is available on the new platform. >> > Have verified the fuse bits, disabled to bootloader >> > and have also written a Blink program in icc-avr >> > which toggles port a bits and in turn does toggle the LEDs. >> > This icc-avr hex file when copied via uisp on a crossbow >> > mica2 toggles the LEDs as well, but the Blink ihex file >> > generated via tinyos copied via icc-avr to the new platform >> > does nothing. >> > >> > any directions on how to proceed or what is the >> > actual load process would be helpful. >> > >> > thanks, >> > - Puru _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
