From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Mandarino Date: Thu, 12 Jul 2007 11:09:19 -0400 Subject: [U-Boot-Users] Interrupts in at91rm9200 u-boot. In-Reply-To: References: <9a7969e20707110120l150cc3b2y382c561fd69f92b5@mail.gmail.com> <406A31B117F2734987636D6CCC93EE3C01CAD749@ehost011-3.exch011.intermedia.net> Message-ID: <4696441F.5000704@endrelia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Joey Oravec wrote: > "Leonid" wrote in message > news:406A31B117F2734987636D6CCC93EE3C01CAD749 at ehost011-3.exch011.intermedia.net... >> I'm trying to implement simple USB device in u-boot for at91rm9200 and >> as a first step I want to see that I can work with interrupts there. I >> added temporary device initialization code to usb_lowlevel_init(): > > I used the USB Device port as a console for my at91sam9261, acting as a > usbser.sys compatible usb-to-serial port. It was a lot easier to use a > polling interface because there was some Atmel sample code available. > > During early startup, I add the usb driver with device_register(). Each > function polls the status register, which works out fine since uboot calls > tstc constantly to look for a new character or putc to display something. > Finally I added a check for the device sense (power) to skip the > initialization completely if we know it's not connected to anything. > > -joey Hi Joey, If possible, I would also be interested in obtaining your U-Boot USB device code. I tried creating a usbdcore_at91.c file to fit into the existing U-Boot usbdcore driver for the TI OMAP1510 a few months ago and didn't get very far, mainly due to the way the AT91 UDP supports various transactions in hardware. Thanks, ../fam -- Frank Mandarino fmandarino(a)endrelia.com Endrelia Technologies Inc. Toronto, Ontario, Canada