Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting "mphidflash Error: USB read error" when I try to upload program to 18f2455 chip #6

Open
GoogleCodeExporter opened this issue Apr 12, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Loading a boot loader with USB access on it using MPLABX & Pickit2. I used 
generic DEMO one from Microchip to compile with a 18f2455 chip set.

2. Placed it in a basic circuit with program & reset capabilities on a 20Mhz 
crystal. Nothing special.

3. Make sure I am root and run the program as rot and load a basic test2.hex
Which only consist of a blinking LED.
./mphidflash -v 2233 -p 7001 -w ../piccode/test2.hex


What is the expected output? What do you see instead?
It does not even get started uploading the test hex file to the pic I get.
 USB HID device found
./mphidflash Error: USB read error

What version of the product are you using? On what operating system?
mphidflash 1.3 : Debian 6.0 stable and Linux Kernel 3.0.8

Please provide any additional information below.
lsusb 
Bus 001 Device 008: ID 2233:7001 RadioShack Corporation 

dmesg
[21964.752426] usb 1-1.4: new full speed USB device number 10 using ehci_hcd
[21964.847784] usb 1-1.4: New USB device found, idVendor=2233, idProduct=7001
[21964.847793] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[21964.847800] usb 1-1.4: Product: Generic HID
[21964.847805] usb 1-1.4: Manufacturer: Test
[21964.850760] generic-usb 0003:2233:7001.0005: hiddev0,hidraw3: USB HID v1.11 
Device [Test Generic HID] on usb-0000:00:13.5-1.4/input0

Original issue reported on code.google.com by facto...@gmail.com on 12 Nov 2011 at 10:30

@GoogleCodeExporter
Copy link
Author

Prerequisites include:
1. The PIC must already be programmed with a compatible Bootloader.
2. The Bootloader must be running ready to receive the update, often there is a 
switch to choose between Bootloader & application.

As Vendor Id / Product Id are not the defaults for the Microchip Bootloader it 
is not clear that a compatible Bootloader is installed in the PIC.

Original comment by tonyna...@gmail.com on 1 Jul 2014 at 5:18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant