Glad to read that in the end you have been able to install the Bus Pirate's driver into your Windows 8.1 x64 system. Well done!
[quote author="mk2soldier"] I have one question though (in fact is only a little thing), in minicom (Linux) and in Tera Term (Windows) when I mistakenly type something in the terminal I am able to use the backspace to delete the erroneous character. In Putty (Windows) I am unable to do so, what do you thing it is causing the problem? Maybe some terminal emulation differences? Thank you![/quote]
I don't use Putty, so I don't know, sorry. Though I believe you are right and actually it's a configuration matter. I did digged a bit the issue perhaps finding a solution. In Terminal/Keyboard you need to set Ctrl-H for the backspace key. So please try it, maybe it can fix your problem. I think that setting is there in every terminal program and then everyone should set it according to their needs.
[quote author="r00tb33r"]You do post in the thread though... ',:-S[/quote]
I have read your questions and I have tried to give some answers. Sadly though I'm not so skilfull on that kind of matters hence I premised the fact. People who read what I wrote need to know that so they can weigh up my speech.
[quote author="r00tb33r"]So you are experiencing a problem now?[/quote]
Ooops, sorry. I myself have bad explained. What I wanted to write is that I never noticed the issues you wrote, I trust on what you have reported though. So until today I haven't the problem but who knows about tomorrow. It's possible I don't experience the issue because until now I never work in that your specific context even if actually I use my Bus Pirate in the way you have wrote when I work on SPI devices. Anyway, no, I haven't the problem you described.
I never used the Bus Pirate as a programmer since I never loaded into it the specific firmwares required and not even I did use it to manage serial protocols, hence I can't write about them. Though, I use flashrom also and just in the specific context you describe and I haven't problems. I'm happy with it, repeat any problem. That's my expereience about those matter. And me too I use Windows 7 64-bit also.
[quote author="r00tb33r"]I would however like to know why my board has an option for a crystal, as I suspect that option was part of Bus Pirate v3 design.[/quote]
I know nothing about it, sorry. Though I guess Ian (and few others) know the right answer.
[quote author="r00tb33r"]Are you implying I should update?[/quote]
Simply I have wrote it because I know, unless otherwise modified and you wrote it is v6.1 r1676, the firmware release you are using has some problem with SPI. In my opinion that isn't the latest firmware, better if you try this:
It's much better expecially for the SPI side. It has been written debugging the v6.3 revision. Actually over the v6.1 there are also the v6.2 and v6.3 revisions. v6,1 isn't the latest and however only that I wrote has been bugfixed for problems facing the SPI's management, no others for what I know.
[quote author="r00tb33r"] Recently however I read about inherent lack of internal clock accuracy and that PICs are said to have inadequate clock accuracy for UART use[/quote]
those I sent are for the PIC side. Anyway like I have already wrote I'm not the right one to talking about your problem. Said that, me too I use my Bus Pirate for that kind of matters and I haven't experienced any problem until now. For reference mine is v3.6 by seeedstudio, although it shouldn't make a difference. Could you please describe precisely the context in which you detect problems (device, protocol, chip, context, software environment ...)? Honestly I don't think the problem is due the FT232RL but I could be wrong. Here is why I'm asking for a more precise description. One last question, are you sure that the firmware you are using really meets your needs? Please, this time try to take a look at these:
Hi Jeroen, OK I understand your purpose. That AT45DB161D-CU chip is the BGA Package Ball-out version (http://snipurl.com/29idcyy) and this complicates things a bit, though. Almost surely the Bus Pirate is able to do the job, perhaps in slowly way but can do it for sure. Anyway the most big problem is that due of the BGA Package Ball-out in use there are not pins where you can easily attach the clips. Maybe on the other side of the board are some sort of copper contacts where is possible to weld wires in order to access to the signals, but sorry I don't know. You need to follow copper's tracks and components on the board looking for the right signals. Actually difficult but not impossible, better if you have the schematic diagram of the board. Perhaps you will also force some wire in order to switch off write protection and/or select-deselect reset pin. Maybe you don't need to unsolder the AT45DB161D-CU. Almost surely the Bus Pirate can't provide power supply for the whole board so you must to power supply it in a separate way. Soldering and desoldering of that kind of package is not easy or trite. Hence I warn you to don't try to do that if you haven't the necessary tools and you aren't pretty expert in the use of them. Good luck!
Normally the possibles address are 128 (there are 7bits for define them, so 2^7=128 different possibility), actually 112 due the fact some bits are reserved. You need to try each one of them looking for the right answer helping yourself with the datasheet. That is what I know but sadly I'm not so skillful in that application field.
I think it would be better if you post your documents here in the forum because may be it is of interest for other and more people may have the answer to your problems. Would you think I'm pushy asking what would you want to get from your AT45DB161D?
Hi Kumba, it is a well known thing. At present you need to tie PGD with PGC by a jumper. From the beginning I have provided my Bus Pirate with a strip welded on the ICSP's connector which as you know it's normally empty. This get me easy to gain bootloader acces on my Bus Pirate. Otherwise you have to downgrade to previous firmware if you don't want use jumper. That's.
Hi tayken, thanks for reply. Ok, I get it. Well done, at least the MOSI problem is out of business now, thank you! Due the fact somewhere somebody have already proposed solutions I'm trying to get a portable version of MPLABX in order to try to fix some old issues (viewtopic.php?f=4&t=5052&start=15). Hoping not damage my Bus Pirate though. Thanks for sharing!
I have downloaded your new firmware. Honestly even before your bug fix, never I have experimented failure using SPI although there was the problem which was described. However fine that now it's gone. From that side for what I can understand all seems to be fine with the new release. I have noticed your firmware is based on 6.3 release, this show the terminal performing "i" (Versioninfo/statusinfo). Am I pushy asking what is new in there? Thanks in advance and thank you very, very much for your fix, improvements and over all this, for sharing it!
in my opinion the Bus Pirate surely can do it. Basically the thing described in your links it is a simple serial/USB interface. You could build it yourself with a few components. Any level shifter such as the MAX232 and few components would be enough, but the Bus Pirate is surely better than a simple RS232 interface and even of the thing described in your links. In my mind only thing you have to pay attention building it yourself it's about signal's level range. This is because seems to me the hard disk you are talking about is 3,3V level on its bus and safety interfacing require that level, 5V could be dangerous for it and interface or computer. So make sure on the right levels you are messing with. Instead using Bus Pirate you don't have to worry about it because it is a 3,3V device with 5V tolerant input. The Bus Pirate is more versatile and sophisticated of any other interfacing device, no way out. It is a little more expensive but the extra money spent will pay off by themselves due the fact that its possibilities are limitless not only if compared to simple serial interfaces. All this in my humble opinion. Please, look at this: http://snipurl.com/28uhldc
Hello Xykon. Thank you very, very much for your hard work! You are really very kind. OK for your kind explanation about the culprit which it's by lowercase used in the hex file. I don't knew it and for me it's useful to know. Well also for the script you wrote in order to convert lowercase to uppercase file which I don't know how to use though because I'm not involved in these kind of matters, sorry about that. About the hex file I used the last one you sent because it was already ready to use. So I downloaded it onto the BP and started the testing. Unluckily it doesn't work as it should. Using the same settings like before in the past, I get the same wrong values when performing macro (1):
2WIRE>(1) ISO 7816-3 ATR (RESET on CS) RESET HIGH, CLOCK TICK, RESET LOW ISO 7816-3 reply (uses current LSB setting): 0x45 0xC8 0x08 0x89 Protocol: unknown Read type: variable length Data units: 32768 Data unit length (bits): 1
Macro (2) doesn't work too, but it was the same in the past when I wrote about this matter. Another thing that perhaps may be help is that now performing command "i" (info) I get this:
2WIRE>i Bus Pirate v3.5 Firmware v6.3-beta1 r2151 Bootloader v4.4 DEVID:0x0447 REVID:0x3046 (24FJ64GA002 B8) 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 SCL SDA - - P P P I I I O I O I GND 3.31V 4.95V 0.00V 5.02V L L H L H POWER SUPPLIES ON, Pull-up resistors ON, Open drain outputs (H=Hi-Z, L=GND) LSB set: LEAST sig bit first, Number of bits read/write: 8 a/A/@ controls CS pin R2W (spd hiz)=( 1 1 ) *----------
which it's a kinda different from what I obtained in the past using the original v6.3-beta1 r2151 firmware and namely:
2WIRE>i Bus Pirate v3.5 Firmware v6.3-beta1 r2151 Bootloader v4.4 DEVID:0x0447 REVID:0x3046 (24FJ64GA002 B8) 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 SCL SDA - - P P P I I I O I I I GND 3.31V 4.94V 0.00V 5.03V L H H H H POWER SUPPLIES ON, Pull-up resistors ON, Open drain outputs (H=Hi-Z, L=GND) LSB set: LEAST sig bit first, Number of bits read/write: 8 a/A/@ controls CS pin R2W (spd hiz)=( 1 1 ) *----------*
notwithstanding I've always used the same settings. I never tire of saying thank you for the commitment and the excellent work although for now it doesn't work as expected. I know it's only the beginning, take no care about the result because without your work there may still be no improvement. It is better a failed attempt than the to do nothing, IMHO. So thanks and thanks again Xykon! I really appreciate very much your work! Many, many thanks!
Hello Xykon. Thank you very much for your attempt to fix the bug, you are very kind. Unluckily I can't test it because when I try to load it in the BP I have this message: ********************************************************** Parsing HEX file [BPv3-firmware-v6.2-r2162.hex] Checksum does not match, line 4 Could not load HEX file, result=-1 ********************************************************** Maybe something wrong in your archive which perhaps may be corrupted or however bad. I don't know. One time more thank you! I appreciate very much your work! Many, many thanks! Hope to read you soon.
