OK Fixed Thanks Was using MISO instead of MOSI for Data! Also Seeed Cable EZ Hook wire was broken, I directly connected with 1 pin wire Jumpers, much better than the clips. I am going to make a special cable just for I2C!
Thanks! I noticed the clock voltage is stuck low, as you can see in the voltage report? They clock and data return high after an address scan. I can make the clock stay low again by typing any number into the terminal, a write. So doesn't seem there is a problem with the BP keeping the clock low? I remember a self test, I will try to run that?
Voltages sfter an address scan that doe not find target....
I have been trying to get I2C BP Mode working. Everything looks great in RealTerm? All commands work per BP manual. I have tried Pic Slaves and master PCBs i made with 16F873a using Microchip Ap note 735. I am having a terrible time. I have looked at clock and data with a scope while the master interrupts every .1S and looks like hardware is working. BP sees data in sniff mode (2) Now just trying to get BP to work with know hardware. I finally hooked up DS1307 and performed the demo I am using 5V from BP to DS1307 and have hooked PU lead to 5V. Pullups ON Does NOT work like demo?
Any other ways to find out why it does not see the DS time chip like the demo shows? Thanks Mike
Here are copies out of RealTerm of the search, Voltage Report, and upgrade info? I have been trying for days now?
Thanks for the extensive reply. I knew nothing about a new Client. I no nothing about Java and am running the exe file in XP. Will someone eventually make a upgraded exe program?
I went to the Bus Pirate location and re-installed USB. System reports "CDC RS-232 Emulator Demo".
Same driver I have seen before from Microchip demo?
The run java batch file gives errors. "Unsupported Class" ......... Exception in Main?
I am running the old exe Client, it has problems connecting to the USB. I push the Reset button a few times on the Sniffer and Re open the exe file until I can get the sniffer to sample? So I am able to Sniff, especially if I leave it going. My first sniffer had a solder or connection problem around the buffer? This one seems OK, even though the Trig LED jumped off.
I missed where this new USB device file is and what is the file name?
Thanks Mike
From Ian
"For firmware v.04 you will need to use the updated .INF file included to reinstall the OLS after updating. The corrected PID is used, and the device now appears as 'Logic Sniffer CDC-232'."
I used ICD2 with one of the latest Pump.hex, no description in file name? Left the option to use fuses in file, not specifying any fuses in ICD2 Programmer.
I did this earlier before your response.
I did the bit stream rom load for 16 Channels x 8K for 0-15 buffered input pins. They are all named the same too. I used the one that makes the inputs 0-15 buffered.
Works after moving USB around and getting it to use a new inf file. It took a few times to have the USB be seen in the PC Client.
I saw a note here with a picture of the Sniffer choosing a new different driver. Although it now works, I never saw that or can find that description in PC System. System says a Microchip driver from 97?
So now I see the 100KHz 8 lines from my test Pic on Ch0-7, haven't checked the upper byte!
When I use the batch program for status check, it still reports the same versions as before?
So it is working so far, I used the cursors and the timing is right on a far as the counter applied to 0-7.
My Trigger LED FELL off somewhere in the CARPET! I gave up looking for the litte sucker! I had a Green one from Mouser and that is working now.
Still wondering about the USB driver? I have problems reconnecting, looks like it is not using the correct driver.
What is the new drivers name and where is it?
I did nothing with the PC Client? Does it use the Jar File with XP, do I just have it in the same directory with the Client? Guess I don't know what you meant about updating the Java Client. I am using the old original program from over a year ago?
I used pump loader and got status. I would like to know for sure what the versions reported are for. I got the standard PUMP HW 1 FW 0.1 BOOT1. So does that mean the Boot loader version 1 is in there?
I then ran the bit stream programming using 16Ch 8K 0-15 on the buffered pins. Now it does not connect. Error running PC Client. I guess that makes sense, I have to do the Pic too?
All the hex files for the pic just seem to be "pump.hex". No version other than a date when use look at properties.
If I try to reprogram the Pic ( I have ICD2), what should I set the fuse settings up for? Can I just program the Boot Loader part of the Pic, I don't know anything about boot loaders. Which Bootloader program would then be used?
I have to look at Vcc on the ICD2. I don't want it using 5V? I will have it NOT use power from ICD2 supply?
Anyone got hints on all this. Which files by date to try?
Thanks, I got another sniffer delivered yesterday as a replacement. I sent the other back as suggested by Ian. Thanks!
I also bought some Seeed Sniffer cables. A little confusing with black wire ground and white channel 0 and so on? I guess they used what wire and clip colors they had available?
I am hooked onto my 8 bit Pic Generator board which fastest bit moves at 100Khz.
Set up with a few signals on Bank 0, I get no triggering when set up on Ch0, when I turn off triggering, I DO SEE signals on BANK 2, if I enable bank 2 and 3? Nothing down on Bank0?
Since this is a new board? I don't know what software versions are in it? Could the PC client program get a self-test built in some day to do some version reading?
So, I wonder why do signals on Bank0 ? The signals on Bank2 are the un-buffered channels correct? I don't know if they are real, or artifacts, or feedthu?
I may try to update? This board was sent a week ago, so I would assume it would be close to the latest?
Sniffer still not showing signs of being dead. My last post is working its way to the bottom with no suggestions. I am testing with 5V Pic counting.
Can someone describe what should happen with the Arm and Trig Leds when they hit the Capture? Before and after? Mine changes once in a while, not each time? Can someone suggest a test that tests each of them?
I since have tried jumping a 3.3V on board voltage to Ch0 and still see low.
Got mine yesterday! 5/11 Took about 2 Weeks shipping to So. Calif, USA, not bad?
Got USB driver working on port 7 and changed speed in system to 115200. Is it necessary to change PC port Baud? Will it even connect if something is wrong here? Seems fine?
Got it connected to pic counting on portb of a 16F873 running 5 volts on a proto board. I have LEDs flashing on some of the slower bits.
Counting at about 1ms delay.
I click the ROKET, set up, and am using only 8 inputs, trigger on 0, and a 2K sample at 10Mhz My ARM led is ON. Both Arm and Trig are RED leds on my board.
Just see all low levels. Nothing high on logic trace.
Tested same counter with Bus Pirate with Sump Client, works great.
A hint might be I don't see the time base at the top change with sample speed? Its scale in in microseconds, so it is not seeing this much slower signal and setting its scale?
I have spent many hours, don't know if it is a dead Sniffer?
Am I putting the signal in the correct pins?
With USB connector on LEFT SIDE, I am using 2nd pin from BOTTOM as CH 0, then up from there. Bottom Pin connected to my pic counter ground. Pins 2-9 for the input channels.
I see pictures on the sites with connectors connected to the top of this connector?
What is the display trace B0 below the ch7 mean? It has continuous hi and low trace lines and says "00" in the middle? Trigger?
OK, I did an update! There were other hex files in the download. IT and ES I guess were for Italian and Spanish? I picked the other one?
Here is what I got now when I initialize! Is that the latest REVID? What is B5?
Is there top view picture with functions of the 10 Pin Interface Connector for Reference. Is there a printable schematic?. I printed out the manual and 101 but am missing finding these.
