[quote author="bearmos"]at least I'm in good company :) Anybody else try out mylar stencils for fine pitch stuff? Honestly, I suspect I did *something* wrong, but. . .when I looked at the stencil under a bit of magnification, it looked pretty rough.[/quote]
here is an Interesting related PDF, It's from Koki. Page 11 has nice photos comparing three stencil production methods, chemical, laser, and electro-form. There is good information, scattered through-out. pg 15 to paraphrase "go slower!" seems a key pattern, it's repeated for other things like the spreader speed.
How are the mylar ones produced? Do you have super cool pictures like the pdf?
A die cut should/would leave a combination of the laser and electro types pictured in this PDF "Angled to one side, and jagged.". The single tapered hole has favorable sides, for differing application methods. Shape "A" has the larger opening in contact with the PCB, optimal for zero standoff. Shape "V", works with standoff to create an extrusion effect.
Using the later shape and/or stand off helps eliminate surface tension of the stencil as a problem area.
NOT TESTED, this time it's going to kick the cat...
Updated against svn r1816. Didn't update my Changelog yet, it's not committed to my local cvs.
Added a configuration #ifdef USE_PICDEVICES for the picdevices.h This has both versions of the pic24 unpack changes, my version is (currently) #ifdef ANDTHEN
Problem areas: TMS not unified(still stamp specific) bs2 code needs adapted to r1816 unpack methods ..?(somethings I forget probably)
Sorry there is a big ugly chunk in PIC24_Read that i'll include the start of below. It's still there/ugly because of, the middle "example" not sure how where or why those 01's showed up, gremlins and goblins.
I'm of no use sorry, but I'm gonna complain about a related issue.
Lets take a nice simple and cheap device and put a USB chip in it that combined with USB license fees, at the least doubles the price. %@$! That whole scenario quite frankly, Pisses me off. Once upon a time PS/2 keyboards cost a whopping 4-5 USD
Google turns up the Belkin and Staples brands, at these prices 15-25 USD I would expect some hardware other than just a passthru cable.
The firmware is the standard release. The software is in the SVN as PiratePICprog/software, the executable produced is picprog.
The supported products/chips/families are IRTOY(pic18f2550) OLS(18F24J50) BP3(24FJ064GA002) BP4(24FJ256GB106)
I'll skip electrical testing and leave that for someone with a degree.
Perform a read test, "picprog -p buspirate -u COM12 -s 115200 -c 18F2550 -t HEX -r read_test.hex" Compare with original, "diff -u irtoy_v22.hex read_test.hex", these should differ only on the last two lines where MPLAB puts the configuration data on multiple lines picprog will have them included on one line.
Perform an erase, "picprog -p buspirate -u COM12 -s 115200 -c 18F2550 -E" Now blank check, "picprog -p buspirate -u COM12 -s 115200 -c 18F2550 -t HEX -r blank_test.hex" And verify, "cat blank_test.hex", don't blink it should scroll past ALOT of F's, at the end it will have 7F don;'t worry about that it's a marker for the configuration data.
Perform a write, "picprog -p buspirate -u COM12 -s 115200 -c 18F2550 -t HEX -W irtoy_v22.hex" Followed with read test(as above)
[quote author="robots"] This is more of HACKING, as compared to Programming/Designing sw :-) [/quote] I didn't design the programming spec or the programming interface, I'm just trying to put them together. :-) So I am OK with that view point. Priorities are functionality, then maintainability, and finally artistry.
[quote author="robots"] The Real solution is to rework the read/write commands together with the Interface definition. Add "generic" interface read/write functions, and setmode to select which pic we are dealing with (already in place). [/quote] Sure I didn't understand, sorry. I interpreted this as "You can simply add PIC32Read/PIC32Write to iface like the others" or "Combine the iface, PIC4* functions and test the mode"
[quote author="robots"] By generic read/write I mean read that can actually read arbitrary register and not only 3consecutive memory spaces (see PIC24). [/quote] I have not IIRC explicitly tried reading arbitrary registers. It, the pic32.c:PIC32_Read, should read anything in the 4gig address space including registers.
Could you expand/explain "(see PIC24)"? I'm not sure where I'm being sent. You mean being able to read bytes of a word?
[quote author="robots"] FW in buspirate doesn't need to "speek" PIC instructions (as does now with the read). Buspirate will only understand the "ICSP" protocol (different ones for different PICs) and the actual programming logic will be inside PiratePICprog. This will also allow for future expansion (PE maybe?) [/quote] Of course the buspirate doesn't need to have the pic functions but it cuts way down on the communication overhead. I use the pure bit banging solution for the pic32 because it fit(just barely ~16 bytes free) in the PBASIC firmware alongside the pic18/24 functions.
The programming executives(PE) are released under the (standard?) Microchip license, the one that says you can only use the software on/with microchip products, and can't be re-distributed. So the license in addition to it(PE32) not working with the (small memory) chips and the time it takes to load (@9600) with all the bit banging, I just kinda of ignored them for this.
[quote author="robots"] This will, of course, require changes in the firmware, message queueing in sw (as done for PIC18), etc.
We could also add PIC32 "commands" to the buspirate's FW, and not care about TMS/TDI bit-manipulation on host.[/quote]
For the V3x firmware there is about 4.5K. I think pic32 ejtag could fit in this, if it reuses OCD functions almost certainly. There are issues with OCD reuse however, the Peekbit is needed inside of Setmode(OCD tapshft?) to check processor state. The OCD code (IIRC) doesn't allow this.
Looking at the CRT2560 service manual, it uses the PD6430 also, on page 56 it gives the power up sequence...
SWVDD is 5v pulsed High Low in 300ms blocks by the controller. Tracing this line backwards from the face-plate leads back to L650(=2r2k) C650(=104) r649(=222), this is just for noise buffering indicated by L650 being a ferrite in the partslist.
Page 48 gives the controller(PE5196A) pinout, and confirms the DPDT uses CMOS voltages.
As might be expected there is no data about the display protocol. Only option is guessing or sniffing a working unit sorry.
This adds support for boot strapping PIC's with a Parallax Basicstamp2, using the Bus Pirate PIC Programming software.
The firmware is included in the filetree as PirateProgv6.bs2 it is written in PBASIC
The patch files are generated against the older (pre april ~10th) code(PiratePICprog). This means there maybe rejects conflicts and other assorted "fun" if applied with robots recent updates. The 1st patch should apply simply with the recent changes but I have not tried yet, the other I recommend against applying to the current revision.
I guess I got lazy typing after I linked the Changelog..
Note the buspirate -> pic32 does not function. 1. The BP OCD mode uses CS as TMS, but CS is MCLR in PIC mode. It could be AUX which is VPP in PIC mode, these are easy to set... in pic32.c
Also of note, the "stampIT2" is set to 9600 bps in the software and firmware to prevent data errors. It's configurable in both, however I ran out of space in firmware to implement any form of command buffer and CRC. So it takes about 8-9 hours to read a mx220, or something crazy long I forgot (YAY) exactly how many. 2-wire 4-phase would make hours into days I fear...
At the top is the "Keyboard" and "Display" data lines KYDT and DPDT. You need to test the voltage, but it looks like they might be 5v (2.2k resistors). Keyboard is easy once you have the voltage you can test and record each key.
Display is where it gets tricky. It's almost safe to assume they didn't reinvent the wheel, that is to say, "It more than likely uses one of the common interfaces".
P.S. image shack sucks they don't deserve ad revenue.. (read as) It's better to attach files to your posts than link offsite, you'll find more people maybe inclined to have a look, images and related text stay connected ect...
Thought I'd answered the legality question but I don't see it. I was referencing an RV, they are kind of particular about using non DOT approved items on vehicles.
Completely non geeklike but, pricing a spare fuel tank seems like the easy way. They are (the smallish tanks for grills) about double the cost if you don't have an exchange tank here.
