Skip to main content

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 - int0x13

1
Bus Pirate Support / Re: strange issue with BP and flash SPI
Flashrom was able to dump the whole chip but with some errors between the dumps, chunks are corrupted, but the most part of the dumps are good, with bus pirate internal supply. USB2 is max 500mA right? So why the BP is not able to supply more than 150mA?
Also i tried just for information to dump with my Willem programmer with chip on the motherboard and it's complaining also about the Power problem, BUT it can ID the chip well. But as the bus pirate the dump is corrupted, and is more corrupted than the flashrom+BP dumps. I tried to use external PSU to power the willem programmer and i was not able to solve the power issue, duno why. But anyways it's working with BP+flashrom+exterrnal PSU on the chip VCC, so it's all good i think.
2
Bus Pirate Support / Re: strange issue with BP and flash SPI
Update to myself: with the help of irc member robot and also Myself(thx to them) i managed to make it work using an external PSU connected to the VCC pin of the chip on the mobo. I guess there is some problem is the PSU W command of the BP it's does not have enough current to power the mobo for some reason.
3
Bus Pirate Support / strange issue with BP and flash SPI
Hello, i have an issue with my bus pirate v3B i dont understand really.
With Flashrom i can detect my chip which is a Winbond SPI W25Q16BV. I have dump the whole chip with flashrom. I want to try to do some interact with the bus pirate shell, and i'm not able at all to detect the chip with the ID instruction. This is because i just cant power ON the chip. I'd like to understand what's wrong. Here is the log:

Code: [Select]
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
x. exit(without change)

(1)>5
Set speed:
 1. 30KHz
 2. 125KHz
 3. 250KHz
 4. 1MHz

(1)>4
Clock polarity:
 1. Idle low *default
 2. Idle high

(1)>
Output clock edge:
 1. Idle to active
 2. Active to idle *default

(2)>
Input sample phase:
 1. Middle *default
 2. End

(1)>
CS:
 1. CS
 2. /CS *default

(2)>
Select output type:
 1. Open drain (H=Hi-Z, L=GND)
 2. Normal (H=3.3V, L=GND)

(1)>2
Ready
SPI>v
Pinstates:
1.(BR)  2.(RD)  3.(OR)  4.(YW)  5.(GN)  6.(BL)  7.(PU)  8.(GR)  9.(WT)  0.(Blk)
GND    3.3V    5.0V    ADC    VPU    AUX    CLK    MOSI    CS      MISO
P      P      P      I      I      I      O      O      O      I
GND    0.94V  0.00V  0.00V  0.00V  L      L      L      H      L
SPI>v
Pinstates:
1.(BR)  2.(RD)  3.(OR)  4.(YW)  5.(GN)  6.(BL)  7.(PU)  8.(GR)  9.(WT)  0.(Blk)
GND    3.3V    5.0V    ADC    VPU    AUX    CLK    MOSI    CS      MISO
P      P      P      I      I      I      O      O      O      I
GND    0.94V  0.00V  0.00V  0.00V  L      L      L      H      L
SPI>W
VREG too low, is there a short?
POWER SUPPLIES OFF
I did a selftest, and it's ok 0 error.
I tried multiple times and it's always the same. Also i just dont understand why i have 1v on the 3.3v when i just select the SPI mode without powering it? And i cant power it because it detects a short?
With the same exact config with flashrom, i have this result:
Code: [Select]
c:>flashrom.exe -V -p buspirate_spi:dev=COM10
flashrom v0.9.6.1-r1644 on Windows 5.1 (x86)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Found Winbond flash chip "W25Q16" (2048 kB, SPI) on buspirate_spi.
No operations were specified.
Probing for Winbond W25Q16.V, 2048 kB: buspirate_sendrecv: write 6, read 4 Sending 0x04 0x00 0x01 0x00 0x03 0x9f, receiving 0x01

0xef 0x40 0x15
RDID returned 0xef 0x40 0x15. probe_spi_rdid_generic: id1 0xef, id2 0x4015
Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on buspirate_spi.
buspirate_sendrecv: write 6, read 3 Sending 0x04 0x00 0x01 0x00 0x02 0x05, receiving 0x01 0x00 0x00
Chip status register is 0x00.
I've tried to measure the voltage during the dump with flashrom and i have constant 3.3v on the bus pirate 3.3v pin.
Here is my config:
Code: [Select]
SPI>i
Bus Pirate v3.b
Firmware v6.2-beta1 r1981  Bootloader v4.4
DEVID:0x0447 REVID:0x3043 (24FJ64GA002 B5)
http://dangerousprototypes.com
CFG1:0xFFDF CFG2:0xFF7F
*----------*
Pinstates:
1.(BR)  2.(RD)  3.(OR)  4.(YW)  5.(GN)  6.(BL)  7.(PU)  8.(GR)  9.(WT)  0.(Blk)
GND    3.3V    5.0V    ADC    VPU    AUX    CLK    MOSI    CS      MISO
P      P      P      I      I      I      O      O      O      I
GND    0.94V  0.00V  0.00V  0.00V  L      L      L      H      L
POWER SUPPLIES OFF, Pull-up resistors OFF, Normal outputs (H=3.3v, L=GND)
MSB set: MOST sig bit first, Number of bits read/write: 8
a/A/@ controls AUX pin
SPI (spd ckp ske smp csl hiz)=( 4 0 1 0 1 0 )
*----------*
Thank you, i really dont understand!
4
USB Infrared Toy / stuck firmware when irtoy.exe process is stopped by ctrl+C
Hello there,
I've experienced an issue that is quite anoying with my usb Ir Toy v2 running firmware 2.2 and irtoy.exe v2.1
(IR TOY Recorder/Player utility v21 (CC-0)):

It seems that if we interrupt a play operation (and maybe other command) using ctrl+C under itoy.exe process, it lets the firmware into a bad state which prevent it to work until unplug/replug the ir toy.
Afterwards, If we try some command onto the com port it will say this:
Code: [Select]
 IR TOY Recorder/Player utility v21 (CC-0)
 http://dangerousprototypes.com

-------------------------------------------------------------------------
 Opening IR Toy on COM14 at 115200bps...
 Cannot Read Firmware Version.

 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 Found Garbage data when reading the firmware version..
 Please re-start this utility again
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Sample command that a ctrl+C prevent future work for me:
irtoy.exe -d COM14 -v -p -f helico_ir
Ctrl+C
...now it's not working until physical unplug/replug.
I've experienced this issue quite often. I talk about the case we cannot open the com port anymore for some reason and it force me to unplug/replug to reload the firmware.
1)Is this a desired/featured behavior?
2)What is the recommended (most stable) firmware at the moment v2.1 or v2.2?

Bonus questions:
3)Is this normal that if i capture 2x or 3x the same key press (dvb-t pinnacle remote controller), i wont have the exact same hex dump file? (same length but not same bytes) I'm talking about same button pressure (small press).
4)Is there a wireshark-like tool that can be used to identify/decode protocol/analyze raw IR dumps?

Thank you,
7
Bus Blaster JTAG debugger / Re: Longest JTAG Cable Possible?
Is there any cable set we can buy @seeedstudio to work with bbv2? With the best length it can work with. I had the surprise when i received my bb to see that it was not sold with a cable set to plug into the 2x10 pins header. I mean like the bus pirate set cable.
9
Bus Pirate Support / Re: Re: miniscope v3
would it be possible to have more than one input into the scope? (i'm not sure it's hardware or software restriction as it's using internally the same command that the d/D command,not sure).
11
Bus Blaster JTAG debugger / Bus Blaster V3?
Hi all dangerous people :)
I've heard that the next bus blaster (version 3) is currently in prepartion, When will it be out? And what will be the improvements?
Thanks
12
Bus Pirate Support / Re: Re: Self test results
I'm just starting, but for now i use it for keyboard mode, logic analyser, oscilloscope. I will maybe try to use the JTAG mode in the future.
14
Bus Pirate Support / Re: Self test results
Self test without the jumper between 5v and vpu:
Code: [Select]
HiZ>~
Disconnect any devices
Connect (Vpu to +5V) and (ADC to +3.3V)
Space to continue
Ctrl
AUX OK
MODE LED OK
PULLUP H OK
PULLUP L OK
VREG OK
ADC and supply
5V(1.75) FAIL
VPU(0.00) FAIL
3.3V(3.21) OK
ADC(3.37) OK
Bus high
MOSI OK
CLK OK
MISO OK
CS OK
Bus Hi-Z 0
MOSI OK
CLK OK
MISO OK
CS OK
Bus Hi-Z 1
MOSI FAIL
CLK FAIL
MISO FAIL
CS FAIL
MODE and VREG LEDs should be on!
Any key to exit

It means regulator broken, which one? VR2, VR3, VR4?
If broken, what can i do? Can i replace it?
15
Bus Pirate Support / Re: Self test results
Hello, since some days, i cannot explain why my buspirate is broken and cant pass the self test. When i first did the self, it was Ok (0 error). Recently i wana play with the keyboard mode so i flashed it with the extra firmware .hex file. So i got the version 5.9. But i failed to have the return into the bp shell when typing keys. That said, i thought it was a good idea to do a self test just in case. And here it is what i got at my big surprise:


Code: [Select]
i
Bus Pirate v3b
Firmware v5.10 (r559)  Bootloader v4.4
DEVID:0x0447 REVID:0x3043 (24FJ64GA002 B5)
http://dangerousprototypes.com
HiZ>~
Disconnect any devices
Connect (Vpu to +5V) and (ADC to +3.3V)
Space to continue
Ctrl
AUX OK
MODE LED OK
PULLUP H OK
PULLUP L OK
VREG OK
ADC and supply
5V(1.69) FAIL
VPU(1.72) FAIL
3.3V(3.31) OK
ADC(3.25) OK
Bus high
MOSI OK
CLK OK
MISO OK
CS OK
Bus Hi-Z 0
MOSI OK
CLK OK
MISO OK
CS OK
Bus Hi-Z 1
MOSI OK
CLK OK
MISO OK
CS OK
MODE and VREG LEDs should be on!
Any key to exit
Do you have any idea what's wrong with my little bp that i was starting to appreciate a lot?
I measured all the voltage on the SMD components on board. Tell me which you need to troubelshoot.
Uvr2=1,85v Uvr3=1,83v Uvr4=5,10v Uc22=3,28v Uc24=1,76v, and i could notfind the R18 resistor, where is it??
Thank you very much for the help!
regards