gnupic: Thread: Re: [gnupic] PICDEM FS USB and Linux tools

On 9/21/07, Xiaofan Chen ####@####.#### wrote:
> If you are using very very latest
> kernel, then you might have to patch the source codes to detach the
> kernel driver to get the demo code working.
> (the demo code is at http://www.varxec.net/picdem_fs_usb/ )
> http://forum.microchip.com/tm.aspx?m=106426)

Working udev files for Ubuntu 6.06/7.04:

####@####.#### cat 026-microchip.rules
#PICKit
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0032", MODE="0660",
GROUP="microchip"
#PICKit2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="0033", MODE="0660",
GROUP="microchip"
#ICD2
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8000", MODE="0660",
GROUP="microchip"
#ICD21
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="8001", MODE="0660",
GROUP="microchip"
#PICDEM FS USB Bootloader
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="000b", MODE="0660",
GROUP="microchip"
#PICDEM FS USB Demo
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="000c", MODE="0660",
GROUP="microchip"
#PICDEM FS USB CDC
SYSFS{idVendor}=="04d8", SYSFS{idProduct}=="000a", MODE="0660",
GROUP="microchip"


Regards,
Xiaofan

Hello Xiaofan :)

First the crash in the GUI should be fixed...

On 9/22/07, Xiaofan Chen ####@####.#### wrote:
> On 9/22/07, Nicolas ####@####.#### wrote:
> > The message may not be clear enough but it just means that this
> > bootloader cannot read the contents of the device memory... You may
> > want to try writing instead.
> >
>
> Ok now I see what it means even though this is strange. The bootloader
> should be able to read the program memory. fsusb works fine with
> reading and writing.

yes indeed. I answer without checking (mixed up with the Tiny
Bootloader). Should be fixed.

> So I tried erasing and writing: both did not work.

Hum I guess the code in Piklab for this bootloader has never been
tested... I tried to fix it. Please try again...

Regards,
Nicolas

On 9/22/07, Xiaofan Chen ####@####.#### wrote:
> >   One thing I've noticed both on the PICDEM and the UWB (Sparkfun)
> > board is if I hold the button down for "boot mode" the entry listed in
> > "lsusb" only stays for some time.  That is, I get the board in boot
> > mode and then keep doing "lsusb" the listing:
> >
> > Bus 002 Device 027: ID 04d8:000b Microchip Technology, Inc.
> >
> >   shows up for about 1-3 seconds then goes away.  Any ideas about
> >   this?  I'm running Debian sid:
>
> Apparently this is a problem with Debian kernel and people
> (including me --under Ubuntu 7.04) are having problem with the
> bootloader and the CDC example (UWB is based on the CDC
> example). It is said  compiling a new vanila kernel will help.
> I have not done that yet. It has been a while that I need
> to recompile a kernel...
> Please also refer to the following threads:
> http://forum.microchip.com/tm.aspx?m=283378
>

Problem solved with vanilla kernel.

If you encounter problems with the USB firmware framework based device
under later kernels, you might want to use the kernel.org vanilla
kernel and build the kernel which disable auto-suspend.

Solution:
http://forum.microchip.com/tm.aspx?m=275422&mpage=2
http://sourceforge.net/mailarchive/forum.php?thread_name=1189786321l.13173l.12l%40mofo&forum_name=libusb-devel

Regards,
Xiaofan

On 9/23/07, Nicolas ####@####.#### wrote:
>
> First the crash in the GUI should be fixed...

The crash of GUI with configuring Piklab is now fixed but reading
with 18F4550 and PICDEM FS USB bootloader caused crash
of the GUI.

Crash log:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240258864 (LWP 23740)]
[KCrash handler]
#6  0x0816b23b in Programmer::Base::doRead (this=0x9e25af8, memory=@0x0,
    range=@0xbf9decf4) at generic_prog.cpp:323
#7  0x0816b333 in Programmer::Base::read (this=0x9e25af8, memory=@0x0,
    range=@0xbf9decf4) at generic_prog.cpp:313
#8  0x081677d9 in Programmer::Manager::read (this=0x87c6030, memory=@0x0,
    range=@0xbf9decf4) at prog_manager.cpp:101
#9  0x08089b11 in MainWindow::read (this=0x873ef68) at toplevel.cpp:986
#10 0x080d30db in MainWindow::qt_invoke (this=0x873ef68, _id=96, _o=0xbf9dedbc)
    at toplevel.moc.cpp:659
#11 0xb69bd88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb69be330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb732b4c9 in KAction::activated () from /usr/lib/libkdeui.so.4
#14 0xb7363cc2 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#15 0xb743106d in KAction::slotPopupActivated () from /usr/lib/libkdeui.so.4
#16 0xb7431331 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#17 0xb69bd88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0xb6d497b0 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#19 0xb69dd81e in QSignal::activate () from /usr/lib/libqt-mt.so.3
#20 0xb6ae3f1b in QPopupMenu::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#21 0xb733234e in KPopupMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.4
#22 0xb69f465d in QWidget::event () from /usr/lib/libqt-mt.so.3
#23 0xb6954a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#24 0xb6956c1e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0xb7118cc2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#26 0xb68e725d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#27 0xb68e5b9f in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3
#28 0xb68e3fac in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#29 0xb68fb180 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#30 0xb696f136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#31 0xb696ef46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#32 0xb6956609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#33 0x08089820 in main (argc=1, argv=0xbf9dfa44) at main.cpp:32


> > So I tried erasing and writing: both did not work.
>
> Hum I guess the code in Piklab for this bootloader has never been
> tested... I tried to fix it. Please try again...

I then tried to use the console version and reading seems to work
but not writing. I need to test again.

One thing is that you need to ignore address below 0x800. For
more detail you may want to refer to the forum thread.
http://forum.microchip.com/tm.aspx?m=106426

By the way, PICkit 1 and PICDEM FS USB (both borrowed from Microchip
Singapore in my previous job in year 2005 and later returned) were
the two things got me started with GNUPIC and USB. And Mark Rages
certainly helped quite a bit during the very beginning. Buying the
PICkit 2 was a good decision for me. Now I do not have the
original PICDEM FS USB board but I have a manual-soldered
cut-down version.

Time flies and it has been two years I played with this.
Some history:
http://forum.microchip.com/tm.asp?m=106426
http://forum.microchip.com/tm.asp?m=106529
http://forum.microchip.com/tm.asp?m=107340

Regards,
Xiaofan

On 9/23/07, Xiaofan Chen ####@####.#### wrote:
> By the way, PICkit 1 and PICDEM FS USB (both borrowed from Microchip
> Singapore in my previous job in year 2005 and later returned) were
> the two things got me started with GNUPIC and USB. And Mark Rages
> certainly helped quite a bit during the very beginning. Buying the
> PICkit 2 was a good decision for me. Now I do not have the
> original PICDEM FS USB board but I have a manual-soldered
> cut-down version.
>
> Time flies and it has been two years I played with this.
> Some history:

Correct the links: Microchip changed tm.asp to tm.aspx.
The forum software is one of the worst...

http://forum.microchip.com/tm.aspx?m=106426
http://forum.microchip.com/tm.aspx?m=106529
http://forum.microchip.com/tm.aspx?m=107340

On 9/23/07, Xiaofan Chen ####@####.#### wrote:
> On 9/23/07, Nicolas ####@####.#### wrote:
> >
> > First the crash in the GUI should be fixed...
>
> The crash of GUI with configuring Piklab is now fixed but reading
> with 18F4550 and PICDEM FS USB bootloader caused crash
> of the GUI.
>

An update: the latest SVN version of Piklab works now with
PICDEM FS USB bootloader.

Xiaofan