Hello, Tony; Good thing there's a solution, but I don't understand what you mean by "remove the ehci_hcd module". Could you be more clear, please?
Thank you! On 4/2/07, Tony Mancill <[EMAIL PROTECTED]> wrote:
Hi Pedro, I use MIB520 boards with Linux and had all kinds of weird problems during programming until I realized that there were usbserial errors in dmesg about communicating with the FTDI chip. The solution for my system was the remove the ehci_hcd module, which was being automatically loaded by the kernel. tony Pedro Almeida wrote: > > Hello all! > > With the help of all and the fantastic tutorial by Miguel Silva ( > http://www.mail-archive.com/[email protected]/msg09493.html > < http://www.mail-archive.com/[email protected]/msg09493.html>), i was able to install everything right on FC6 (or so i believe). > > Right now was was doing the basic programming for the Blink application, > and i came up with an error for which i have found plenty of complains, > but short on solutions (mainly because it's mostly related to TinyOS1.x > and mib510 boards). > > So I do, as supposed > > $make micaz install mib520,/dev/ttyUSB1 > > gives me this: > > [EMAIL PROTECTED] Blink]# make micaz install mib520,/dev/ttyUSB1 > mkdir -p build/micaz > compiling BlinkAppC to a micaz binary > ncc -o build/micaz/main.exe -Os -finline-limit=100000 -Wall -Wshadow > -Wnesc-all -target=micaz -fnesc-cfile=b > uild/micaz/app.c -board=micasb -fnesc-dump=wiring > -fnesc-dump='interfaces(!abstract())' -fnesc-dump='refere > nced(interfacedefs, components)' > -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm > compiled BlinkAppC to build/micaz/main.exe > 2410 bytes in ROM > 51 bytes in RAM > avr-objcopy --output-target=srec build/micaz/main.exe build/micaz/main.srec > avr-objcopy --output-target=ihex build/micaz/main.exe build/micaz/main.ihex > writing TOS image > cp build/micaz/main.srec build/micaz/main.srec.out > installing micaz binary with dapa > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --erase > pulse > Atmel AVR ATmega128 is found. > Erasing device ... > pulse > Reinitializing device > Atmel AVR ATmega128 is found. > > Fuse High Byte set to 0xd9 > > Fuse Extended Byte set to 0xff > sleep 1 > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff > --upload if=build/micaz/main.srec.out > pulse > Atmel AVR ATmega128 is found. > Uploading: flash > > Fuse High Byte set to 0xd9 > > Fuse Extended Byte set to 0xff > sleep 1 > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff > --verify if=build/micaz/main.srec.out > pulse > Atmel AVR ATmega128 is found. > Verifying: flash > flash error at address 0x0: file=0x0c, mem=0x00 > flash error at address 0x1: file=0x94, mem=0x00 > flash error at address 0x2: file=0x49, mem=0x00 > flash error at address 0x4: file=0x0c, mem=0x00 > .... > flash error at address 0x968: file=0x18, mem=0x00 > flash error at address 0x969: file=0x95, mem=0x00 > > Fuse High Byte set to 0xd9 > > Fuse Extended Byte set to 0xff > rm -f build/micaz/main.exe.out build/micaz/main.srec.out > > > one of the solutions proposed doing, to clean the memory or something : > $uisp -dprog=dapa --erase, that gave > > pulse > Probably the AVR MCU is not in the RESET state. > Check it out and run me again. > > i have no idea what this means. > i have also tried using mib510 instead of mib520, keeping the /ttyUSB1, > but didnt work either. > > please, any solutions? > > thanks once more! > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
