1
Open Bench Logic Sniffer / Re: Nothing captured
Also: the scratch is UNDER the lacquer, so certainly in manufacturing, not afterwards.
Show Posts
This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.
Messages - Fozzy Vis
Also: the scratch is UNDER the lacquer, so certainly in manufacturing, not afterwards.
2
Open Bench Logic Sniffer / Nothing captured
I bought the OLS a long time ago but never got it to work.
Updating the bitstream/firmware works flawless, connecting to it through various clients as well, but nothing is captured. Just solid lines. Strange thing is that the captured states seem to be random high or low, but always consistent within one capture on one channel. CH1 could be high with CH2 low, and next capture they would have different values.
After a loooong time (moved and renovated a house) I dug it out again since I need a LA shortly and didn't want to by a Logic one since I had already bought a OLS.
Updated the latest software I found on the frontpage, but no luck when generating a signal with my BP. Checked the same signal with a scope and signal is fine.
LED's are like they should be according to the manuals. Tried the SUMP and the OLSFront software.
After browsing through the forums, I found one guy who had one and posted pictures of a scratch across the board. I never noticed it untill really looking for it now, but I have a comparable scratch at allmost the same spot. Under the ARM led, between TRIG and R8 and then going to C20 and C19 (board rev 1.01). Can post pics if necessary.
Anything else I can try? Would like to try to get this one to work before I buy a Logic.
thanks!
3
Bus Pirate Support / Re: I2C, no ACK at random times
The first write (which came after a read) didn't work properly, but afterwards, no problems anymore.
I'm not 100% sure if I understand your explanation about the 18F afterwards (with the double "0").
Still wonder if the problem is just with me or not..
Code: [Select]
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: NO
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x54
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: NO
WRITE: 0x00 GOT ACK: NO
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
4
Bus Pirate Support / Re: I2C, no ACK at random times
5
Bus Pirate Support / Re: I2C, no ACK at random times
Code: [Select]
(1) >4
MODE SET
Set speed:
1. Slow(~5KHz)
2. Fast(~50KHz)
SPEED>(1) >1
I2C routines Copyright (C) 2000 Michael Pearce
Released under GNU General Public License
I2C READY
I2C>W
POWER SUPPLIES ON
I2C>p
1. Pullup off
2. Pullup on
(1) >2
PULLUP RESISTORS ON
I2C>i
Hack a Day Bus Pirate v2go
http://www.buspirate.com
Firmware v2.1-nightly
DEVID:0x04 0x47
REVID:0x30 0x03
CFG1:0xF9 0xDF
CFG2:0x3F 0x7F
*----------*
POWER SUPPLIES ON
VOLTAGE MONITOR: 5V: 5.0 | 3.3V: 3.3 | VPULLUP: 5.0 |
AUX: DEFAULT SETTING (AUX PIN)
High-Z outputs (H=input, L=GND)
PULLUP RESISTORS ON
BITORDER CONFIGURATION NOT ALLOWED IN THIS MODE
*----------*
I2C>(1)
Searching 7bit I2C addresss space.
Found devices at:
0xD0 0xD1
I2C>[0xd0 0 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
I2C>[0xd0 1 0]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
WRITE: 0x00 GOT ACK: YES
I2C STOP CONDITION
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: YES
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x00
I2C STOP CONDITION
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: NO
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x01
I2C STOP CONDITION
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: NO
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x03
I2C STOP CONDITION
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: NO
WRITE: 0x01 GOT ACK: NO
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x02
I2C STOP CONDITION
I2C>[0xd0 1 [0xd1 r]
I2C START CONDITION
WRITE: 0xD0 GOT ACK: YES
WRITE: 0x01 GOT ACK: NO
I2C START CONDITION
WRITE: 0xD1 GOT ACK: YES
READ: 0x54
I2C STOP CONDITION
I2C>
Same problems, with both speed settings. Also using [0xd0 1] [0xd1 r] doesnt change anything...
6
Bus Pirate Support / Re: I2C, no ACK at random times
I'll need some time figuring it out but will try as soon as possible.
I suppose I'll find the nightly build on the SVN/Google code page, and have to compile it with MPLab and then update it with the bootloader. I've seen instructions for the last part on your site, will look into the compiling asap.
7
Bus Pirate Support / Re: I2C, no ACK at random times
The datasheet specifies an Fscl of max 100 KHz, I'm not sure if that's fast or not.
I've also tried writing it like: [0xd0 1] [0xd1 r], which gave the same problems as well.
Please also consider it could be a stupid mistake from my side. However it's strange that is sometimes works and sometimes not...
8
Bus Pirate Support / I2C, no ACK at random times
First of all, I'm a mere beginner in electronics without a real college type of background. All I did was read books/magazines/sites/... so there are things that I should know about, but don't. Take it as a disclaimer
I'm trying to interface a DS1307 RTC chip with the Bus Pirate. I'm doing this on a breadboard. I've connected the Vcc to the bus pirate +5V, the ground to the ground line, and the Vpu to it's own +5V line.
The crystal is in the same holes as the pins from the IC, I've read that it's good practice to keep distances between an ic and an crystal as short as possible.
Vbat is pulled to ground, as stated in the datasheet when a backup battery isn't used.
There's a 100uF cap over the GND/Vcc lines, I know it's about filtering but don't really know exactly why it's needed. Will read up on that later.
If needed: this is what I got from the terminal with the "i" command:
*----------*
POWER SUPPLIES ON
VOLTAGE MONITOR: 5V: 5.0 | 3.3V: 3.3 | VPULLUP: 5.0 |
AUX: DEFAULT SETTING (AUX PIN)
High-Z outputs (H=input, L=GND)
PULLUP RESISTORS ON
BITORDER CONFIGURATION NOT ALLOWED IN THIS MODE
*----------*
This is what I did:
-initialised I2C mode ("m", "4")
-enabled the pullups ("p", "2")
-enabled power supplies ("W")
-checked pullup voltage ("i"), is fine at 5.0
-checked IC adress on I2C bus ("(1)"), found devices at 0xD0 and 0xD1 (sometimes it also finds something at 0xD2, not sure why?)
-Started the oscillator and set seconds to zero: "[0xd0 0 0]" Gives 3 times ACK
-Defined the minutes to zero as well, just to make sure it starts there "[0xd0 1 0]", all good again
And this is where I'm not sure I'm doing everything ok and the errors start
- "[0xd0 1 [0xd1 r]" gives 2 writes, one read that seems to return a valid number (depending on the delay between the setting to zero en querying the minutes)
-Then trying that same line again gives some errors. Write 0xD0 gives an ACK, the 0x01 DOESN't give ACK, the read gets an ACK seems like it could be fine.
-Trying it again a minute later gets the same faults, then a third time doesn't give an ACK on the writes, gives a ACK on the read, but returns an invalid number (all of a sudden we're supposed to be 17 minutes later?)
I have used this IC with a easyPIC5 board from MikroElektronika and things went smooth then. I'm not sure what I'm doing wrong here.
I've used the BusPirate to talk to a 7221 SPI to 7segment Decoder without any problems.
It seems to be a bit random, and I don't really know where to look anymore... Any hints/tips/thoughts?
If there's any info I forgot to mention, please ask!