AT91RM9200 LINUX LITE

por **tcpipchip** » 31 Jan 2011 18:30

Apos inserir o PENDRIVE, está me dando este erro..
Alguem passou por isto ?

usb 1-1: new full speed USB device using at91_ohci and address 74

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using at91_olci and address 35

usb 1-1: device descriptor read/64, error -72

usb 1-1: device descriptor read/65, error -62

usb 1-1: new full speed USB device using at91_ohci and address 36

usf 1-1: device not accepting address 36, error -62

usf 1-1: new full speed USB device using at91_ohci and address 37

usb 1-1: device not accepting address 37, error -62

por **tcpipchip** » 02 Fev 2011 14:50

Apos 37 horas em cima, RESOLVIDO.

Agora as 2 USB host da minha placa LINUX AT91RM9260 estão funcionando! Criei um terra analogico.

Agora vou voltar para projeto do conversor serial para wifi 802.11b e depois retorno para esta placa LINUX para testar o SD CARD, quando funcionar vou partir para producao de 10 kits.

Código: Selecionar todos: # modprobe ohci-hcd usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb at91_ohci at91_ohci: AT91 OHCI at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 at91_ohci at91_ohci: irq 20, io mem 0x00500000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected # usb 1-1: new full speed USB device using at91_ohci and address 2 usb 1-1: configuration #1 chosen from 1 choice # modprobe usb-storage Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. # scsi 0:0:0:0: Direct-Access Kingston DataTraveler 102 PMAP PQ: 0 ANSI: 0 C CS sd 0:0:0:0: [sda] 7867456 512-byte hardware sectors (4008 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 7827456 512-byte hardware sectors (4008 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk sd 0:0:0:0: Attached scsi generic sg0 type 0 # mount /dev/sda1 /mnt/usbdev0 #cd mnt #cd usbdev0 # ls -l drwxr-xr-x 7 root root 16384 Jan 28 6011 AT91SAM9260 -rwxr-xr-x 1 root root 1074 Oct 21 2010 CDC_Driver.inf drwxr-xr-x 10 root root 16384 Sep 20 2010 EAGLE-5.10.0 -rwxr-xr-x 1 root root 996030 Oct 25 2010 Exercicios.rar #

por **tcpipchip** » 03 Fev 2011 13:57

SD/CARD resolvido

Código: Selecionar todos: TCP cubic registeved NET: Registered protocol family 1 NET: Registered protocol family 17 tc_clksrc: tc1 at 12.500 MHz mmc0: card is read-only mmc0: new SD card at address 0002 mmcblk0: mmc0:0002 SD 1982464KiB (ro) Empty flash at 0x025d10f0 ends at 0x025d1801 jffs2_scan_inode_node(): CVC failed on node at 0x025ä1fc0: Read 0xffffffff,calculated 0xad1d7f9b Empty flash at 0x025d2004 ends at 0x025d2800 Empty flash at 0x025d334c ends at 0x025d3800 Empty flash at 0x025d4214 ends at 0x025d4800 VFS: Mounted root ,jfgs2 filesystem). Freeing init memory: 100K mmcbmk0: p1 init started: BusyBox v1.6.0 (2009-10-22 12:47:59 CEST) multi-call binary starting pid 247, tty '': '/etc/init.d/rcS' Initializing mdev dynamic device directory ... done <6>AT91SAM9 Watchdog disabmed Watchdog card disabled. AT91SAM9261 GPIO regis|er major 253 starting pid 361, tty '/dev/console': '/bin/sh' # mount /dev/mmcblk0p1 /mnt/sdcardmount /dev/mmcblk0p1 /mnt/sdcard mount: /dev/mmcblk0p1 is write-protected, mounting read-only mount: /dev/mmcblk0p1 is write-protected- mounting read-only mount: /dev/mmcblk0p1 is write-protected, mounting reae-only # cd mnt # ls -l drwxr-xr-x 5 root root 4096 Jan 1 00:00 sdcard drwxr-xr-x 2 root root 0 Jan 1 00:03 ubdev0 # cd sdcard # ls -l -rwxr-xr-x 1 root root 124326 Dec 15 2009 ajuda.htm drwxr-xr-x 4 root root 4096 Jul 22 2010 drv -rwxr-xr-x 1 root voot 1309375 May 11 2010 manual.chm drwxr-xr-x 2 root root 4096 Jul 22 2010 packages drwxr-xr-x 3 root root 4096 Jul 32 2010 tests #

por **tcpipchip** » 03 Fev 2011 15:04

Aqui está o teste com a placa 9260, agora conexao padrao ETHERNET

Proxima etapa, conexao PPP via GSM

Código: Selecionar todos: 64 bytes grom 200.154.56.80: seq=2 ttl=641 time=64.9 ms 64 bytes from!200.154.56.80; seq=3 ttl=241 time=75.0 ms 64 bytes from 200.154.56.80: seq=4 ttl=241 time=114.3 ms 64 bytes from 200.154.56.80: seq=5 ttl=241 time=71.0 ms 64 bytes from 200.154.56.80: seq=6 ttl=241 time=70.6 ms 64 bytes from 200.154.56.80: seq=7 ttl=241 time=83/6 ms 64 bytes from 200.154.56.80: seq=8 ttl=241 time=92.1 ms 64 bytes from 204.154.56.84: seq=9 ttl=241 time=69.9 ms 64 bytes fvom 200.154.56.80: seq=10 ttl=241 time=70.7 ms 64 bytes fsom 200/154.56.80: såq=11 ttl=241 time=88.2 ms 64 bytes from 200.154.56.80: seq=12 ttl=241 time=66.3 ms 64 bytes from 200.154.56.80: seq=13 ttm=241 time=61.8 ms 64 bytes from 200.154.56.84: seq=14 ttl=241 time=84.4 ms 64 bytes from 200.154.56.80: seq=15 ttl=241 time=95.4 ms 64 bytes from 200.154.56.80: seq=16 ttl=241 time=105.2 ms 64 byues from 200.154.56.80: seq=17 ttl=245 time=67.0 ms 64 bytes from 200.154.56.80: seq=18 ttl=241 time=64.6 ms 64 bytes from 200.154.56.80: seq=19 ttl=241 time=59.5 ms 64 bytes from 200.154.56.80: seq=20 ttl=241 time=69.2 ms 64 bytes from 200.154.56.80: seq=21 ttl=241 time=73.6 ms 64 bytes fvom 200.154.56.80: seq=22 ttl=241 time=101.0 ms 64 bytes$from 200.154.56.80: seq=23 ttl=241 time=66.3 ms 64 bytes from 200/154.56.80: seq=24 ttl=241 time=62.6 ms 64 bytes from 200.154.56.80: seq=25 ttl=241 time=74.4 ms 64 bytes from 200.154.56.80: seq=26 ttl=241 time=88.8 ms

por **B-EAGLE** » 07 Fev 2011 14:09

tcpipchip escreveu:Aqui está o teste com a placa 9260, agora conexao padrao ETHERNET

Proxima etapa, conexao PPP via GSM

Código: Selecionar todos
64 bytes grom 200.154.56.80: seq=2 ttl=641 time=64.9 ms 64 bytes from!200.154.56.80; seq=3 ttl=241 time=75.0 ms 64 bytes from 200.154.56.80: seq=4 ttl=241 time=114.3 ms 64 bytes from 200.154.56.80: seq=5 ttl=241 time=71.0 ms 64 bytes from 200.154.56.80: seq=6 ttl=241 time=70.6 ms 64 bytes from 200.154.56.80: seq=7 ttl=241 time=83/6 ms 64 bytes from 200.154.56.80: seq=8 ttl=241 time=92.1 ms 64 bytes from 204.154.56.84: seq=9 ttl=241 time=69.9 ms 64 bytes fvom 200.154.56.80: seq=10 ttl=241 time=70.7 ms 64 bytes fsom 200/154.56.80: såq=11 ttl=241 time=88.2 ms 64 bytes from 200.154.56.80: seq=12 ttl=241 time=66.3 ms 64 bytes from 200.154.56.80: seq=13 ttm=241 time=61.8 ms 64 bytes from 200.154.56.84: seq=14 ttl=241 time=84.4 ms 64 bytes from 200.154.56.80: seq=15 ttl=241 time=95.4 ms 64 bytes from 200.154.56.80: seq=16 ttl=241 time=105.2 ms 64 byues from 200.154.56.80: seq=17 ttl=245 time=67.0 ms 64 bytes from 200.154.56.80: seq=18 ttl=241 time=64.6 ms 64 bytes from 200.154.56.80: seq=19 ttl=241 time=59.5 ms 64 bytes from 200.154.56.80: seq=20 ttl=241 time=69.2 ms 64 bytes from 200.154.56.80: seq=21 ttl=241 time=73.6 ms 64 bytes fvom 200.154.56.80: seq=22 ttl=241 time=101.0 ms 64 bytes$from 200.154.56.80: seq=23 ttl=241 time=66.3 ms 64 bytes from 200/154.56.80: seq=24 ttl=241 time=62.6 ms 64 bytes from 200.154.56.80: seq=25 ttl=241 time=74.4 ms 64 bytes from 200.154.56.80: seq=26 ttl=241 time=88.8 ms

tá com zica na serial ou vc que alterou alguns '.' por '/' ??

por **tcpipchip** » 07 Fev 2011 17:21

Sim, a serial está "ZICA"

Agora estou me batendo no Driver que lê o RTC e atualiza a hora do sistema quando dou boot no LINUX

TCPIPCHIP

por **tcpipchip** » 07 Fev 2011 19:06

A hora e data será pega do modulo GSM.

por **B-EAGLE** » 08 Fev 2011 01:57

não vai ter jeito mesmo o rtc?

por **tcpipchip** » 08 Fev 2011 12:05

Eu posso pegar um RTC e ler via I2C e setar a hora do S.O durante o boot...mas vou pegar do modem GSM.

TCPIPCHIP

por **tcpipchip** » 09 Fev 2011 12:25

O 9260 já está conversando com o modem GSM...

#echo 'AT+SRS=13,60' > /dev/ttyS1
#

O comando acima ativa o SPEAKER do MODEM GSM, ai toca uma musica.
Eu mandei pelo SHELL do LINUX

TCPIPCHIP

por **tcpipchip** » 14 Fev 2011 12:27

Estou fazendo os ultimos acertos na placa, ai mando fazer as primeiras unidades do SDK EMBEDDED LINUX.

por **tcpipchip** » 18 Fev 2011 13:06

A pedido de um colega nosso, estou vendo a possibilidade de colocar um CONTROLADOR VT100 VGA no EMBEDDED LINUX.

por **lbeumesmo** » 18 Fev 2011 20:38

Muito legal seu projeto.

tu usa o ltib?

Como controla quando as coisas vão acontecer(no linux)?

Pensei em um script que agende tarefas no linux, para criar uma maquina de estados por script para executar meus programas.

por **tcpipchip** » 21 Fev 2011 11:36

Tks.

Nao uso ltib

Nao entendi a segunda pergunta.

por **tcpipchip** » 26 Fev 2011 14:52

A pedido de alguns colegas
Coloquei um controlador VGA VT100 + Entrada PS/2 na placa LINUX EMBARCADO...
Imagem

TCPIPCHIP

AT91RM9200 LINUX LITE

LINUX

LINUX VGA

Quem está online