JTAG Serial Cable run 1 for Milkymist One
Contents |
Schedule
| Item | Description | Planned Start date | Status |
|---|---|---|---|
| KiCad design file, | Done | ||
| KiCad to BOM | KiCad generates lst file | Done | |
| KiCad to Digi-Key/Mouser/Sharism | boom generates shopping list / Order status | All parts get ordered. | Done |
| KiCad to gerber/drill file | The process of settings on KiCad Gerber and Drill Files | Done | |
| Determine PCB panelized | http://en.qi-hardware.com/wiki/File:M1_jtag_panel_run1_illustration_revised.pdf, source. | Done | |
| Single gerber-Out to PCB maker | check list, pcb maker sent a panel gerber file back | Done | |
| KiCad to AI file | How to generate KiCad Automatic Insertion File? coordinate files(front /back ) of parts. | Done | |
| PCB Back Check | Confirm PCB quality, panel top, panel bottom | Done | |
| Engineering files to SMT manufacturer | BoM/AI/panel gerber/placement top/placement bottom/parts polarity top/released parts' qty information/page 58 of Soldering reflow profile in FT2232HQ-REEL | This date prior to SMT date | Done |
| Some photos SMT/Through hole process | PCBA is estimated arrival on January 3th, 2011 | Within end week of 2010 | Done |
| Tests & Results | Done |
Some photos
The P2 2x7pins JTAG header being placed manually. Notice that the package status of P2 incoming I chose is tubes. So there's no way to be picked/placed by auto machine. This is the case that was not an good design for manufacturing. It must be improved later on design beginnings and layout changes like choosing the part with locator posts if having further runs later.
The operator did the place work followed my instruction to her. This was escaped the foreword seriously if I didn't provide them an clear instruction on placing RIGHT at CENTER of pad of P2 footprint EXACTLY. I can imagine it should have made completed wrong and nonbalanced placement if I have not reminded.
Firstly we planed to mount back side of panel then front side. The serial female header 1x 4 pins of P1 was missing due to different process. We only planed to produce 100 pcs, so this P1 part will be manually soldered later. Notice that an optical Fiducial Mark placed above 'C35' Silkscreen this time is totally non-function since I leaved a width of 5mm only for V-Cut side board. But their smt machine FUJI XP-243EUNIQ50e3165046bd91df-nowiki-00000002-QINU1UNIQ50e3165046bd91df-nowiki-00000003-QINU's conveyor blocked 3mm which covered this mark, so smt machine can not do an calibration of setting origin point. This happens since we changed smt vendor and got not enough info from different machine. This will always be paid more attentions on this. But we were lucky because we had have P1 though holes. So use P1's holes to be as the origin of the coordinates. So either placing the design/placement within 'single' gerber or shifting the mark a bit.
Tests and Results
- Step1: Make sure the pod connected on a stable +5V[2] supplied by mini-USB cable and its current is good without huge consumptions. See Fig. 3. Finally got one board with D2 failure.
- Step2: Update Milymist One JTAG/Serial pod firmware
Follow instructions of Update JTAG firmware on Windows[3], use FTDI_Prog tool to update following data:
Vendor ID : 20B7 Product ID : 0713 Manufacturer : Qi Hardware Product Description : MIlkymist One JTAG/Serial Port A Hardware : 245 FIFO
The result of Step 2, got one board can not be detected in FTDI_Prog. See pictures below:
- Step3: Test on Milkymist One board
1, Make sure Milkymist One board power is off.
2, Plug JTAG/Serial pod into Milkymist One board.
3, Plug USB mini-B cable into pod's usb connector.
4, Open a terminal session, type dmesg. There must be two usb devices shown below:
[ 6956.054952] usbcore: registered new interface driver usbserial [ 6956.055192] USB Serial support registered for generic [ 6956.055479] usbcore: registered new interface driver usbserial_generic [ 6956.055482] usbserial: USB Serial Driver core [ 6956.061052] USB Serial support registered for FTDI USB Serial Device [ 6956.061755] ftdi_sio 6-1:1.0: FTDI USB Serial Device converter detected [ 6956.061806] usb 6-1: Detected FT2232H [ 6956.061809] usb 6-1: Number of endpoints 2 [ 6956.061812] usb 6-1: Endpoint 1 MaxPacketSize 64 [ 6956.061814] usb 6-1: Endpoint 2 MaxPacketSize 64 [ 6956.061816] usb 6-1: Setting MaxPacketSize 64 [ 6956.063218] usb 6-1: FTDI USB Serial Device converter now attached to ttyUSB0 [ 6956.063270] ftdi_sio 6-1:1.1: FTDI USB Serial Device converter detected [ 6956.063302] usb 6-1: Detected FT2232H [ 6956.063304] usb 6-1: Number of endpoints 2 [ 6956.063307] usb 6-1: Endpoint 1 MaxPacketSize 64 [ 6956.063309] usb 6-1: Endpoint 2 MaxPacketSize 64 [ 6956.063312] usb 6-1: Setting MaxPacketSize 64 [ 6956.066249] usb 6-1: FTDI USB Serial Device converter now attached to ttyUSB1 [ 6956.066294] usbcore: registered new interface driver ftdi_sio [ 6956.066296] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
5, Use binary file boot.bin[4] and open another new session of terminal, type following command to wait:
adam@adam-laptop:~/m1_adam/rc2_test$ flterm --port /dev/ttyUSB1 --kernel boot.bin [FLTERM] Starting...
Notice: My linux laptop doesn't tell if pod is inserted, so entered two commands at my site. Then type 'dmesg', should show above messages.
root@adam-laptop:/home/adam# rmmod ftdi_sio root@adam-laptop:/home/adam# modprobe ftdi_sio vendor=0x20b7 product=0x0713
Meanwhile recorded my environment here:
root@adam-laptop:/home/adam# uname -a Linux adam-laptop 2.6.32-27-generic #49-Ubuntu SMP Wed Dec 1 23:52:12 UTC 2010 i686 GNU/Linux
Links
- Milkymist JTAG-serial daughterboard
- http://www.milkymist.org/wiki/index.php?title=Flashing_the_Milkymist_One
- http://www.milkymist.org/wiki/index.php?title=JTAG
- Sharism prototype runs