Re: [Flashforth-devel] flashforth on p18f4550 - No usb?
Brought to you by:
oh2aun
|
From: Scott B. <sba...@al...> - 2011-10-14 00:10:01
|
On 11-10-12 02:38 PM, Mikael Nordman wrote:
> The first thing to try is to skip the IDLE_MODE in the config file.
> The IDLE_MODE causes the PIC to poll the USB tranceiver
> too seldom.
Gak! I realized now that my first response was to Mikael, and not to the
list. My apologies.
I've disabled IDLE_MODE in p18f-main.cfg.
> Newer and faster PCs seems to have a problem with that !
>
> Are xtal and pll setting correct ?
I've set:
constant clock=d'20000000'
in p18f-main.cfg, recompiled, and re-flashed. Same thing's happening on the
USB bus.
Looking in p18f2455-2550-4455-4550.cfg, I'm seeing:
config PLLDIV = 3 ; 12 MHz XT xtal
config CPUDIV = OSC1_PLL2 ; 48 MHz cpu clock
config USBDIV = 2 ; USB clock from 96 MHZ PLL divided by 2
I'd imagine these aren't correct, but I've no clue how they should be set.
Mike, thanks for the help so far. This looks SO cool if I can get it running!
Cheers,
Scott
>
> Mike
>
> On 13.10.2011 20:46, Scott Balneaves wrote:
>> Hello!
>>
>> I'm trying to get flashforth going on a p18f4550. I've bought an experimenter
>> board from Olimex:
>>
>> http://www.olimex.com/dev/pic-usb-4550.html
>>
>> I've git-cloned the latest flashforth, and installed the MPLAB tools
>> that came with my PICKIT2 burner.
>>
>> I create a new project, add ff18_usb.asm, PF18_USB_REG.asm, and add the
>> FF_USB_18F4550.lib file. Build appears to be successful: ends with build
>> succeeded. I program the device and verify it, and it tells me the device
>> is programmed successfully and verifies successfully.
>>
>> I plug the board into my Linux box (64 bit Ubuntu 11.04), and here's what
>> I'm seeing in dmesg:
>>
>> [13843.230116] usb 6-3: new full speed USB device using ohci_hcd and address 17
>> [13843.370133] usb 6-3: device descriptor read/64, error -62
>> [13843.630123] usb 6-3: device descriptor read/64, error -62
>> [13843.890117] usb 6-3: new full speed USB device using ohci_hcd and address 18
>> [13844.040144] usb 6-3: device descriptor read/64, error -62
>> [13844.300133] usb 6-3: device descriptor read/64, error -62
>> [13844.560128] usb 6-3: new full speed USB device using ohci_hcd and address 19
>> [13844.980126] usb 6-3: device not accepting address 19, error -62
>> [13845.130133] usb 6-3: new full speed USB device using ohci_hcd and address 20
>> [13845.550143] usb 6-3: device not accepting address 20, error -62
>> [13845.550197] hub 6-0:1.0: unable to enumerate USB device on port 3
>>
>> I'm assuming it's supposed to look like a USB serial device that I can
>> connect minicom to port /dev/ttyUSB0 or the like.
>>
>> Any ideas on what I'm doing wrong?
>>
>> Cheers,
>> Scott
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>> _______________________________________________
>> Flashforth-devel mailing list
>> Fla...@li...
>> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
--
Scott L. Balneaves | Eating words has never given me indigestion.
Systems Department | -- Winston Churchill
Legal Aid Manitoba |
|