https://proghq.org/w/api.php?action=feedcontributions&feedformat=atom&user=Mcmaster 2026-04-15T01:51:50Z User contributions MediaWiki 1.41.1 https://proghq.org/w/index.php?title=BPM_Socket&diff=971 2024-07-05T21:33:57Z

<p>Mcmaster: </p> <hr /> <div>[[Category:BPM]]<br /> [[Category:Hardware]]<br /> [[Category:Accessories]]<br /> <br /> Look them up here: http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/<br /> <br /> Ex: http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SM56TB<br /> <br /> This is also interesting: http://www3.bpmicro.com/DeviceList.nsf/128c573fb6a3a6d9862579b4006de31f!OpenView<br /> <br /> Info: [[http:''www.bpmmicro.com/your-socket-solution/|http:''www.bpmmicro.com/your-socket-solution/]]<br /> <br /> Device list: http://web.archive.org/web/20120925022829im_/http://www.bpmicro.com/pdf/engineering-device-list.pdf<br /> <br /> More info here: https://www.adaptsys.com/support-services/bpm-support/faq<br /> <br /> = Standard =<br /> <br /> Used on older programmers like BP series<br /> <br /> == Firmware analysis ==<br /> <br /> Case study on SM48D EEPROM<br /> * samples<br /> ** 4 good<br /> ** 1 with corrupt EEPROM, mostly ignored<br /> * unk00: always 17<br /> * name: always SM48D<br /> * namei<br /> ** no generally noticeable pattern<br /> ** 0xF0000000 always set<br /> * unk1E: Relatively small number that varies, possibly serial number<br /> * pad22: always 0 <br /> * unk26: always 0<br /> * unk44: always 0x55aa<br /> * unk46: always 0xa233<br /> * unk48: always 1<br /> * pad4A: always 0<br /> <br /> Generally seems that there is a structure being used which is initialized to 0. Some fields are unused, keeping them at 0. Anything beyond the structure is 0xFF<br /> <br /> == SM32TC ==<br /> <br /> [[File:mcmaster_bpm_sm32tc_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm32tc_top_open.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm32tc_btm.jpg|frameless]]<br /> <br /> <br /> == SM44QC ==<br /> <br /> [[File:mcmaster_bpm_sm44qc_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm44qc_top_open.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm44qc_btm.jpg|frameless]]<br /> <br /> <br /> == SM48D ==<br /> <br /> [[File:mcmaster_bpm_sm48d_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm48d_btm.jpg|frameless]]<br /> <br /> <br /> https://x.com/johndmcmaster/status/1171332341244940288<br /> <br /> https://github.com/JohnDMcMaster/prog-cad/tree/master/bpm-socket/sm48d<br /> == SM56TB ==<br /> <br /> [[File:Ln bpm sm56tb btm.jpg|frameless]]<br /> [[File:Ln bpm sm56tb top.jpg|frameless]]<br /> <br /> http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SM56TB<br /> <br /> == SM100TQ ==<br /> <br /> [[File:mcmaster_bpm_sm100tq_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm100tq_btm.jpg|frameless]]<br /> <br /> <br /> == SM-84UP ==<br /> <br /> [[File:mcmaster_bpm_sm-84up_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm-84up_top_open.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm-84up_top_open_template.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm-84up_templates.jpg|frameless]]<br /> <br /> <br /> == SM-208CQSX-Actel ==<br /> <br /> [[File:mcmaster_bpm_sm-208cqsx-actel_top.jpg|frameless]]<br /> <br /> <br /> == ASM100FBG ==<br /> <br /> [[File:mcmaster_bpm_sm-_bga_hsc_top.jpg|frameless]]<br /> [[File:mcmaster_bpm_sm-_bga_hsc_btm.jpg|frameless]]<br /> <br /> Found at HSC. ASM100FBG is found in the EEPROM<br /> <br /> http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/ASM100FBG<br /> <br /> &quot;BGA(100), 1.0 mm pitch&quot;<br /> <br /> Only supports 2 devices<br /> <br /> == SMAH48DL1 ==<br /> <br /> [[File:Bpm SMAH48DL1.jpg|frameless]]<br /> <br /> Closest I could find: SMAH20P (http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SMAH20P)<br /> <br /> Which is for a &quot;PLCC(20...80)&quot;. Weird<br /> <br /> = FX =<br /> <br /> = FX2, FX4 =<br /> <br /> = Purchasing =<br /> <br /> https://www.artisantg.com<br /> * Has a large inventory, but they want $350 per socket</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=930 2022-12-22T06:28:25Z

<p>Mcmaster: </p> <hr /> <div>==WCH-link==<br /> <br /> Debug header<br /> <br /> #BO<br /> #*94 BOOT0<br /> #3V3<br /> #*no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> #SWDCLK<br /> #*PA14/SWCLK<br /> #SWDIO<br /> #*PA13/SWDIO<br /> #ground<br /> #BOOT<br /> #*Drives SM16306SJ (shift register) latch enable (LE) Z to prevent bus contention with programmer<br /> #**SR output is shared with one of the WCH-Link pins (SWDCLK/SWDIO, forget which)<br /> #**U5 pin 4<br /> #**SM16306SJ - serial to parallel shift register / LED driver? Datasheet: [https://datasheet.lcsc.com/lcsc/2105241639_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.pdf] Product page: [https://www.lcsc.com/product-detail/LED-Drivers_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.html]<br /> #**4 =&gt; LE<br /> #**BOOT1 ???<br /> #*<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> ID 4348:55e0 WinChipHead<br /> This is USB bootloader mode<br /> <br /> Document at https://raw.githubusercontent.com/openwch/ch32v307/main/EVT/PUB/CH32V30xEVT%20Evaluation%20Board%20Manual.pdf indicates that for USB bootloader mode: &quot;(1) BOOT0 to VCC, BOOT1 to the ground, connect to PC via serial port or USB&quot;<br /> <br /> WCHISPStudio/WCHISPTool (the separate programming tool, accessible via Tools-&gt;WCH In-System Programmer in the IDE) sees the device when jumpered this way. The IDE doesn't, so it might be necessary to use this tool to do the programming.<br /> <br /> == Dev flow ==<br /> https://github.com/davidcarne/t48-dummy-c-program<br /> <br /> Sample flow for Linux doing LED blink<br /> <br /> ==Unbrick==<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=929 2022-12-21T19:14:51Z

<p>Mcmaster: </p> <hr /> <div>===WCH-link===<br /> <br /> Debug header<br /> <br /> #BO<br /> #*94 BOOT0<br /> #3V3<br /> #*no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> #SWDCLK<br /> #*PA14/SWCLK<br /> #SWDIO<br /> #*PA13/SWDIO<br /> #ground<br /> #BOOT<br /> #*Drives SM16306SJ (shift register) latch enable (LE) Z to prevent bus contention with programmer<br /> #**SR output is shared with one of the WCH-Link pins (SWDCLK/SWDIO, forget which)<br /> #**U5 pin 4<br /> #**SM16306SJ - serial to parallel shift register / LED driver? Datasheet: [https://datasheet.lcsc.com/lcsc/2105241639_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.pdf] Product page: [https://www.lcsc.com/product-detail/LED-Drivers_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.html]<br /> #**4 =&gt; LE<br /> #**BOOT1 ???<br /> #*<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> ID 4348:55e0 WinChipHead<br /> This is USB bootloader mode<br /> <br /> Document at https://raw.githubusercontent.com/openwch/ch32v307/main/EVT/PUB/CH32V30xEVT%20Evaluation%20Board%20Manual.pdf indicates that for USB bootloader mode: &quot;(1) BOOT0 to VCC, BOOT1 to the ground, connect to PC via serial port or USB&quot;<br /> <br /> WCHISPStudio/WCHISPTool (the separate programming tool, accessible via Tools-&gt;WCH In-System Programmer in the IDE) sees the device when jumpered this way. The IDE doesn't, so it might be necessary to use this tool to do the programming.<br /> ===Unbrick===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=924 2022-12-21T06:05:51Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> #* 94 BOOT0<br /> # 3V3<br /> #* no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> #* PA14/SWCLK<br /> # SWDIO<br /> #* PA13/SWDIO<br /> # ground<br /> # BOOT<br /> #* U5 pin 4<br /> #* SM16306SJ<br /> #* https://www.lcsc.com/product-detail/LED-Drivers_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.html<br /> #* 4 =&gt; LE<br /> #* BOOT1?<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> What exactly is this? <br /> <br /> ID 4348:55e0 WinChipHead<br /> <br /> I think this is WchLink built into chip?<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=923 2022-12-21T06:04:12Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> #* 94 BOOT0<br /> # 3V3<br /> #* no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> #* PA14/SWCLK<br /> # SWDIO<br /> #* PA13/SWDIO<br /> # ground<br /> # BOOT<br /> #* U5 pin 4<br /> #* SM16306SJ<br /> #* https://www.lcsc.com/product-detail/LED-Drivers_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.html<br /> #* 4 =&gt; LE<br /> #* BOOT1?<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=922 2022-12-21T06:03:14Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> # 3V3<br /> #* no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> # SWDIO<br /> # ground<br /> # BOOT<br /> #* U5 pin 4<br /> #* SM16306SJ<br /> #* https://www.lcsc.com/product-detail/LED-Drivers_Shenzhen-Sunmoon-Micro-SM16306S_C2830324.html<br /> #* 4 =&gt; LE<br /> #* BOOT1?<br /> <br /> <br /> <br /> Package pin assignment<br /> * PA13/SWDIO<br /> * PA14/SWCLK<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=921 2022-12-21T06:02:17Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> # 3V3<br /> #* no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> # SWDIO<br /> # ground<br /> # BOOT<br /> #* BOOT1?<br /> <br /> <br /> Package pin assignment<br /> * PA13/SWDIO<br /> * PA14/SWCLK<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=920 2022-12-21T06:01:43Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> # 3V3<br /> ** no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> # SWDIO<br /> # ground<br /> # BOOT<br /> ** BOOT1?<br /> <br /> <br /> Package pin assignment<br /> * PA13/SWDIO<br /> * PA14/SWCLK<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=919 2022-12-21T06:01:31Z

<p>Mcmaster: </p> <hr /> <div>=== WCH-link ===<br /> <br /> Debug header<br /> # BO<br /> # 3V3<br /> * no 3.3V on PCB. I guess connect to WCH-Link 3V3?<br /> # SWDCLK<br /> # SWDIO<br /> # ground<br /> # BOOT<br /> * BOOT1?<br /> <br /> <br /> Package pin assignment<br /> * PA13/SWDIO<br /> * PA14/SWCLK<br /> <br /> <br /> boot to high pin =&gt; seems to enable USB even with SWD plugged in<br /> <br /> <br /> === Unbrick ===<br /> <br /> In theory we have all firmware (system ROM, bootloader, main firmware) and should be able to unbrick devices. However, I was unable to restore my devices<br /> <br /> Theory: unrick issue is firmware is not at correct .hex location. Things that didn't seem to work to get firmware .hex file:<br /> <br /> objcopy --input-target=binary --output-target=ihex --set-start 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex<br /> <br /> objcopy --input-target=binary --output-target=ihex --change-addresses 0x08000000 t48_bootrom_2022-06-30.bin t48_bootrom_2022-06-30.hex <br /> <br /> objcopy --input-target=binary --output-target=ihex t48_bootrom_2022-06-30.bin temp.hex<br /> objcopy --change-addresses 0x08000000 temp.hex t48_bootrom_2022-06-30.hex</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=918 2022-12-21T05:58:04Z

<p>Mcmaster: </p> <hr /> <div>=== Unbrick ===</div>

Mcmaster https://proghq.org/w/index.php?title=T48&diff=917 2022-12-21T05:56:23Z

<p>Mcmaster: Created page with &quot;Test&quot;</p> <hr /> <div>Test</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=916 2022-12-21T05:56:15Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *[[T48]] universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> **Also known as autoelectric, but this name seems to have fallen out of use<br /> *minipro: software to control TL866 hardware<br /> **Notably the proprietary Windows software, but the Linux FOSS CLI software is also called &quot;minipro&quot;<br /> **Confusingly the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307VCT6<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=RF-3148_Supported_Devices&diff=915 2022-11-14T21:26:21Z

<p>Mcmaster: </p> <hr /> <div><br /> <br /> RF.INF<br /> <br /> RFA.INF<br /> <br /> ==PAL==<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Vendor<br /> !Product<br /> !Read<br /> Secure<br /> !Special<br /> Protect<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Mcmaster https://proghq.org/w/index.php?title=RF-3148_Supported_Devices&diff=914 2022-11-14T21:07:02Z

<p>Mcmaster: </p> <hr /> <div>RF.INF<br /> <br /> RFA.INF<br /> <br /> == PAL ==<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Vendor<br /> !Product<br /> !Read<br /> Secure<br /> !Special<br /> Protect<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Mcmaster https://proghq.org/w/index.php?title=RF-3148_Supported_Devices&diff=913 2022-11-14T19:07:11Z

<p>Mcmaster: Created page with &quot;sdf&quot;</p> <hr /> <div>sdf</div>

Mcmaster https://proghq.org/w/index.php?title=RunFei&diff=912 2022-11-14T19:07:03Z

<p>Mcmaster: </p> <hr /> <div>[[Category:RunFei]]<br /> [[Category:Vendor]]<br /> <br /> These programmers are notable for containing functions to read out protected ICs (via gentle voltage glitching) and permanently destroy test circuitry to prevent security voltage glitching (via strong voltage glitching)<br /> <br /> was: http://www.runfei.com.cn . According to archive.org, the website was active from roughly 2000 to 2008. From archive.org:<br /> <br /> &quot;Beijing Xinrunfei Electronic Technology Co., Ltd. (formerly Beijing Runfei Electric Co., Ltd.) developed and produced RF-1800, RF810, RF-1848 USB intelligent universal programmers since 1998, 1999, and 2002&quot;<br /> <br /> =RF-910=<br /> <br /> In 2018 [https://www.vipprogrammer.com/runfei-m-25 RF-910 for sale for $85]<br /> <br /> <br /> =RF-1800=<br /> <br /> RF-1800/810 manual: http://web.archive.org/web/20110313101116/http://www.runfei.com.cn:80/software/rf.doc<br /> <br /> In 2018 [https://www.vipprogrammer.com/runfei-m-25 RF-1800 for sale for $179]<br /> <br /> <br /> =RF-2148=<br /> <br /> &quot;Luckily the PLDs were early GALs which could have their code extracted using a Run-Fei RF-2148USB IC programmer. The software for the programmer allows for some early PLDs with security issues to be copied regardless of the security bit being set. Henry was in luck and was able to read and duplicate all the PLDs for this board.&quot; https://wiki.reactivemicro.com/GS-RAM_Plus<br /> <br /> Lord_Nightmare: &quot;...the rf-2148 (which runfei 'recalled' and had some very broken english explanation why)...&quot;<br /> <br /> balrog: &quot;if you can fine an rf-2148 it doesn’t need the [K51 special protect] adapter&quot;<br /> <br /> <br /> =RF-3148=<br /> <br /> https://www.vipprogrammer.com/rf3148-usb-universal-programmer-intelligent-chip-tester-programmer-784<br /> <br /> &quot;this (no longer available) RunFei RF-3148 programmer I have has a &quot;Read secured IC&quot; function and a &quot;Special protect&quot; function for at89c52. however the documentation indicates that the latter requires an [K51] adapter that's unobtainium. there's two claimed additional security measures for at89c5x: &quot;otp security&quot; and &quot;data line killing&quot;&quot;<br /> <br /> [[RF-3148 Supported Devices]]<br /> <br /> [[File:runfei_3148_other_menu.png]]<br /> <br /> [[File:runfei_3148_protect_dialogue.png]]<br /> <br /> [[File:runfei_3148_unsecure_dialogue.png]]<br /> <br /> In 2018 [https://www.vipprogrammer.com/runfei-m-25 RF-3148 for sale for $229]<br /> <br /> <br /> <br /> &lt;nowiki&gt;https://www.tradekorea.com/product/detail/P575662/RF-3148-USB-Universal-programmer-intelligent-Chip-Tester.html&lt;/nowiki&gt;<br /> <br /> &quot;RF-3148 usb programmer is full drive intelligent general programmer, it brings together xinrun fly more than ten years experience in design development, periof two years development accomplish. <br /> <br /> elaborate the products with all kinds of device programming needed all drive resource, including 48pin socket, road power supply voltage, burn programmed write voltage controlled programmed / i o signal, revisions, bordels oscillation clock, noise filter, surge strangulating etc, user secondary hardware ( adapter input ) reduses to minimum overhead .<br /> <br /> attainment approximation 's burning speed, automatically detect pin access to undesirable, ensure the programming safe and efficient, all power device used low manufacturing, abopt lower power consumption. complete mainframe usb mouth power supply work, circumscribing forsook the / ac dc adapter, making machine weight lighter and more small, easy to carry .<br /> <br /> support eeprom: PLD: GAL, ATF, PALCE, PEEL; EPROM: serial port and parallel por EEPROM; FLASHROM, MPU: 51 serial（87C, 97C, W78/77, AT89C/87F/80F, P89C, SST89C, IS89,P87LPC7XX…… ）, AT90S,ATTINY, ATMEGA, PIC12/16/17, EM78P, MDT20, Z86E……<br /> <br /> Test support: TTL74/54 serial, CMOS40/45 serial, SRAM, 8155, 8255, 8253, 6821, subscriber can test vector table expand test model <br /> <br /> special: encryption can to at89 series mcu, carry on otp recoverability don't encryption, the use of safe and reliable two step encryption way, encryption after not affect the bus function <br /> <br /> direct reading: decryption can to GAL16V8/A/B、20V8/A/B、22V10/B、PALCE16V8H/20V8H direct reading of declassified, and have &quot;door touchdowns fuse-element map &quot; to &quot; logic expression &quot; automatic conversion function.&quot;<br /> <br /> &lt;br /&gt;<br /> <br /> ==Software==<br /> Final software release from archive.org page:<br /> <br /> https://web.archive.org/web/20080225150423/http://www.runfei.com.cn/new_page_2.htm<br /> <br /> <br /> RF-3148(USB) software Chinese and English Win98/me/NT/W2K/XP software Publication date: 2008.02.20<br /> <br /> RF-2148(USB) software Chinese and English Win98/me/NT/W2K/XP software Publication date: 2008.02.20 (Old users need to upgrade the USB driver)<br /> <br /> RF-2148(PRT) software Chinese and English Win98/me/NT/W2K/XP software Publication date: 2008.02.20<br /> <br /> RF-1800mini(USB) software Chinese and English Win98/me/NT/W2K/XP software Publication date: 2008.02.20<br /> <br /> RF-910(USB) software Chinese and English Win98/me/NT/W2K/XP software Publication date: 2008.02.20<br /> <br /> RF-1800mini software Chinese and English Win95/98/me/NT/W2K/XP software Publication date: 2007.06.18<br /> <br /> RF-910 software Chinese and English Win95/98/me/NT/W2K/XP software Publication date: 2007.06.18<br /> <br /> RF-1800 software DOS version software Publication date: 2000.4.28<br /> <br /> RF-1800 software Full Chinese Win95/98/me/NT/W2K/XP software Publication date: 2003.3.26<br /> <br /> RF-810 software DOS version software Publication date: 2000.4.28<br /> <br /> RF-810 software Full Chinese Win95/98/me/NT/W2K/XP software Publication date: 2003.3.31<br /> <br /> RF-510 software Full Chinese Win95/98/me/NT/W2K/XP software Publication date: 2003.3.31<br /> <br /> RF-1600 Software DOS version software Publication date: 1999.7.8<br /> &lt;br /&gt;</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=911 2022-11-09T19:53:49Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> **Also known as autoelectric, but this name seems to have fallen out of use<br /> *minipro: software to control TL866 hardware<br /> **Notably the proprietary Windows software, but the Linux FOSS CLI software is also called &quot;minipro&quot;<br /> **Confusingly the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307VCT6<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=910 2022-11-08T02:25:28Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> **Also known as autoelectric, but this name seems to have fallen out of use<br /> *minipro: software to control TL866 hardware<br /> **Notably the proprietary Windows software, but the Linux FOSS CLI software is also called &quot;minipro&quot;<br /> **Confusingly the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=909 2022-11-08T02:24:31Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware<br /> **Notably the proprietary Windows software, but the Linux FOSS CLI software is also called &quot;minipro&quot;<br /> **Confusingly the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=908 2022-11-08T02:22:48Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware<br /> **Although the original TL866 also says &quot;minipro&quot; on it<br /> **The Linux CLI software is also called &quot;minipro&quot;<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=Bitrot&diff=903 2022-08-26T23:46:25Z

<p>Mcmaster: </p> <hr /> <div><br /> Techniques for dumping bit-rotten and/or damaged EPROMs:<br /> <br /> Bit-rotten roms are EPROMs/EEPROMs/flash where the floating gate charges have decayed from age/light exposure below the threshold to reliably read as the 'high' state. On most EPROM based devices, a high floating gate charge indicates a 0 bit, so this means the values will read as 0xFF instead of the proper value.<br /> <br /> There are several techniques to try to recover bit-rotten data like this:<br /> <br /> Change temperature. Ex: People have reported success using a hair dryer or heat-gun on parts. This seems to work better than freezing parts does, maybe by 'boosting' via thermal noise the floating gate charge readout value?<br /> Lower reference voltage: Lowering the VCC/Reference voltage from 5v to below 4.97v or so lowers the 'threshold' for reading back floating gate charges, which can recover some bits which are just below the threshold. Too low of a voltage may make the chip malfunction, too high will not have any effect. To prevent potential damage to the chip by having address/control lines driven higher than VCC, the reference input 'high' (ViH) voltage for all pins should be lowered simultaneously, but this might not always be necessary.<br /> Multiple reads and binary ANDing or 'voting' of the bits: dumping a chip several dozen/hundred times and having each dump 'vote' for whether a given bit is 1 or 0, the most popular votes winning. Binary AND is simpler, but this causes problems if a bit should read as 1 and erratically reads as 0.<br /> <br /> Combining 2 or more of these techniques is significantly more effective than using them separately, so people have had much better luck both heating and simultaneously under-volting chips than doing either one separately.<br /> <br /> <br /> Damaged Chips:<br /> <br /> There are more or less two classes of damage to an IC which will prevent it from reading: Damage to the leadframe and bond wires, and damage to the die itself.<br /> <br /> Heat might help for leadframe/bond wire damage (if it cannot be directly/permanently repaired with conductive epoxy or solder, etc) as it may make the metal expand enough to make contact with the other side it was broken off of.<br /> <br /> <br /> Voltage injection<br /> <br /> https://twitter.com/Manawyrm/status/1563178483165016065<br /> <br /> ==McMaster - Phil B experiment 2019==<br /> Took 3 bit rotted (sunlight exposure?) EPROMs and tried to recover bits. Used [[TL866#External VDD control|modified TL866]] to control VDD during readout. One of the EPROMs had a largish &quot;sweet spot&quot; that resulted in stable readout. However, Phil was unable to confirm that the dump improved data quality. Its unclear to me (McMaster) if the data was actually not good or that it was simply hard to tell if it had been improved.<br /> ==See also==<br /> [[EPROM]]: has some (limited) information on EPROM erase profiles. Might be useful for understanding sunlight damage profiles</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=902 2022-08-24T06:26:07Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |[https://github.com/radiomanV/TL866/tree/master/docs Y]<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=901 2022-08-24T05:55:12Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |N<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |N<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> *FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> *FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=900 2022-08-24T05:50:57Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |N*<br /> |<br /> |FOSS firmware: some progress was made, but generally abandoned in favor of T48/T56<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> Where:<br /> <br /> * FOSS CLI: https://gitlab.com/DavidGriffith/minipro/<br /> * FOSS firmware: https://github.com/JohnDMcMaster/open-tl866/<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=899 2022-08-24T05:49:35Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |<br /> |<br /> |<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/269 N]<br /> |<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |[https://gitlab.com/DavidGriffith/minipro/-/issues/174 N]<br /> |<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=898 2022-08-24T05:09:53Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |<br /> |<br /> |<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |<br /> |<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |<br /> |<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=897 2022-08-24T05:09:17Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> ==Comparison==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |PIC18F87J50<br /> |N/A<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |PIC24FJ256<br /> |N/A<br /> |Y<br /> |<br /> |<br /> |<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |CH32V307<br /> |N/A<br /> |Y<br /> |<br /> |<br /> |CPU from McMaster teardown<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |PIC32<br /> |Spartan 6<br /> |<br /> |<br /> |<br /> |Board info: https://www.youtube.com/watch?v=PHD7OXDYzrQ<br /> |}<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=896 2022-08-24T05:05:43Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> XGecu is a line of programmers from Haikou Xingong Electronics Co.,Ltd. Their devices include:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> &lt;br /&gt;<br /> <br /> == Comparison ==<br /> They have a table on their website: http://www.xgecu.com/<br /> <br /> Some additional info below<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Product<br /> !Socket<br /> !Other port<br /> !CPU<br /> !FPGA<br /> !FOSS<br /> CLI<br /> !FOSS<br /> firmware<br /> !Schematic<br /> !Notes<br /> |-<br /> |TL866A<br /> TL866CS<br /> |DIP40<br /> |ICSP<br /> |<br /> |<br /> |Y<br /> |Y<br /> |Y<br /> |TL866A and TL866CS are same hardware w/ different software<br /> |-<br /> |TL866 II PLUS<br /> |DIP40<br /> |ICSP<br /> |<br /> |<br /> |Y<br /> |<br /> |<br /> |<br /> |-<br /> |T48<br /> |DIP40<br /> |something<br /> |<br /> |<br /> |Y<br /> |<br /> |<br /> |<br /> |-<br /> |T56<br /> |DIP48<br /> |something else<br /> |<br /> |<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=Haikou_Xingong_Electronics&diff=895 2022-08-24T04:57:32Z

<p>Mcmaster: Mcmaster moved page Haikou Xingong Electronics to XGecu</p> <hr /> <div>#REDIRECT [[XGecu]]</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=894 2022-08-24T04:57:32Z

<p>Mcmaster: Mcmaster moved page Haikou Xingong Electronics to XGecu</p> <hr /> <div>[[Category:Vendor]]<br /> <br /> Autoelectric is a Chinese firm that produces the following devices:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=893 2022-08-24T04:57:23Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> Autoelectric is a Chinese firm that produces the following devices:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong including TL866, TL866II, T48, and T56<br /> *minipro: software to control TL866 hardware. Although the original TL866 also says &quot;minipro&quot; on it<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=892 2022-08-24T04:56:00Z

<p>Mcmaster: </p> <hr /> <div>[[Category:Vendor]]<br /> <br /> Autoelectric is a Chinese firm that produces the following devices:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T48 universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *Haikou Xingong Electronics Co.,Ltd: official company name<br /> *XGecu: line of programmers made by Haikou Xingong<br /> *TL866: hardware device<br /> *minipro: software to control TL866 hardware<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=Autoelectric&diff=891 2022-08-24T04:54:58Z

<p>Mcmaster: Mcmaster moved page Autoelectric to Haikou Xingong Electronics</p> <hr /> <div>#REDIRECT [[Haikou Xingong Electronics]]</div>

Mcmaster https://proghq.org/w/index.php?title=XGecu&diff=890 2022-08-24T04:54:58Z

<p>Mcmaster: Mcmaster moved page Autoelectric to Haikou Xingong Electronics</p> <hr /> <div>[[Category:Vendor]]<br /> <br /> Autoelectric is a Chinese firm that produces the following devices:<br /> <br /> *[[TL866]] universal programmer (widely cloned, replaced by the TL866 II PLUS)<br /> *[[TL866 II PLUS]] universal programmer<br /> *T56 universal programmer<br /> *Various CAN bus equipment (out of scope for this wiki)<br /> <br /> Glossary:<br /> <br /> *XGecu/autoelectric: company name<br /> *TL866: hardware device<br /> *minipro: software to control TL866 hardware<br /> <br /> ==External links==<br /> <br /> *[http://www.autoelectric.cn autoelectric.cn] (Official site used in TL866 marketing)<br /> *[http://www.xgecu.com/ xgecu.com] (Official site used in TL866II Plus marketing)</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=889 2022-05-28T21:45:25Z

<p>Mcmaster: </p> <hr /> <div>==Quick start==<br /> You will need:<br /> <br /> *Ubuntu 20.04<br /> *Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> **ATMEGA328P blank / in any state<br /> *DuPAL power supply and USB serial<br /> *avrdude compatible programmer<br /> **I used avrispmkII<br /> *PAL16L8<br /> *Optional: tool to flash PAL16L8<br /> **TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> ===Quick test===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> wget https://proghq.org/media/dupal/trackstar128_u33_pal16l8a2nc.jed<br /> <br /> Testing:<br /> <br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> ==Testing==<br /> <br /> With no chip in it takes about 9 minutes and gives a mask of 00. Be suspicious if you see this<br /> <br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> <br /> ==Building==<br /> <br /> ===MCU===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> ===Analyzer===<br /> <br /> sudo apt install maven<br /> mvn compile<br /> sudo mvn install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> == Logic minimization ==<br /> The recommended flow is to use espresso. Unfortunately this program is a bit old and crusty<br /> <br /> java -jar target/espresso-converter-0.0.3-jar-with-dependencies.jar ~/doc/ext/dupal/u33.json out.esp<br /> <br /> <br /> found this but it crashes under most usage scenarios...I had to work to find something that didn't<br /> <br /> git clone &lt;nowiki&gt;https://github.com/JackHack96/logic-synthesis.git&lt;/nowiki&gt;<br /> &lt;br /&gt;</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=888 2022-05-28T18:50:01Z

<p>Mcmaster: </p> <hr /> <div>==Quick start==<br /> You will need:<br /> <br /> *Ubuntu 20.04<br /> *Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> **ATMEGA328P blank / in any state<br /> *DuPAL power supply and USB serial<br /> *avrdude compatible programmer<br /> **I used avrispmkII<br /> *PAL16L8<br /> *Optional: tool to flash PAL16L8<br /> **TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> ===Quick test===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> wget https://proghq.org/media/dupal/trackstar128_u33_pal16l8a2nc.jed<br /> <br /> Testing:<br /> <br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> ==Testing==<br /> <br /> With no chip in it takes about 9 minutes and gives a mask of 00. Be suspicious if you see this<br /> <br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> <br /> ==Building==<br /> <br /> ===MCU===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> ===Analyzer===<br /> <br /> sudo apt install maven<br /> mvn compile<br /> sudo mvn install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> == Logic minimization ==<br /> The recommended flow is to use espresso. Unfortunately this program is a bit old and crusty<br /> <br /> java -jar target/espresso-converter-0.0.3-jar-with-dependencies.jar ~/doc/ext/dupal/u33.json out.esp<br /> <br /> <br /> found this but it crashes under most usage scenarios...I had to work to find something that didn't<br /> <br /> git clone &lt;nowiki&gt;https://github.com/JackHack96/logic-synthesis.git&lt;/nowiki&gt;<br /> &lt;br /&gt;</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=887 2022-05-28T10:20:46Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> wget https://proghq.org/media/dupal/trackstar128_u33_pal16l8a2nc.jed<br /> <br /> Testing:<br /> <br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> <br /> ==Testing==<br /> <br /> With no chip in it takes about 9 minutes and gives a mask of 00. Be suspicious if you see this<br /> <br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> mvn compile<br /> sudo mvn install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=Readpal&diff=886 2022-05-28T09:59:55Z

<p>Mcmaster: Created page with &quot;Main page: http://techno-junk.org/readpal.php PCB: https://github.com/pascalorama/paldumper &lt;br /&gt;&quot;</p> <hr /> <div>Main page: http://techno-junk.org/readpal.php<br /> <br /> PCB: https://github.com/pascalorama/paldumper<br /> <br /> &lt;br /&gt;</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=885 2022-05-24T05:09:57Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> wget https://proghq.org/media/dupal/trackstar128_u33_pal16l8a2nc.jed<br /> <br /> Testing:<br /> <br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> <br /> ==Testing==<br /> <br /> With no chip in it takes about 9 minutes and gives a mask of 00. Be suspicious if you see this<br /> <br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 00<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> nvm compile<br /> sudo nvm install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=884 2022-05-21T22:08:50Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> wget https://proghq.org/media/dupal/trackstar128_u33_pal16l8a2nc.jed<br /> <br /> Testing:<br /> <br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> nvm compile<br /> sudo nvm install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=883 2022-05-21T22:03:18Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> Burn trackstar128_u33_pal16l8a2nc.jed (FIXME: instructions)<br /> <br /> Testing:<br /> Turn off DuPAL<br /> Insert PAL into 20 pin socket<br /> Turn on DuPAL<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> Both the activity green light and the &quot;20 pin active&quot; LED should turn on<br /> Let run. Took just over a minute on my setup<br /> Note: .json file will not be produced<br /> <br /> Sample output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Starting IO type detection... This could take a while.<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - detectIOTypeMask -&gt; Currently detected mask is 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Detected the following IO as Outputs mask: 07<br /> [main] INFO info.hkzlab.dupal.analyzer.board.boardio.DuPALAnalyzer - Now, turn OFF and ON again the DuPAL to reset the PAL and run this tool again by specifying the mask <br /> and output file.<br /> <br /> Now re-run with the suggested mask option:<br /> <br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar /dev/ttyUSB0 16L8 out.json 07<br /> <br /> Sample output:<br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> nvm compile<br /> sudo nvm install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=882 2022-05-21T21:43:30Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> mkdir ~/dupal<br /> cd ~/dupal<br /> sudo apt-get install -y avrdude minicom<br /> wget https://proghq.org/media/dupal/optiboot_v8.0_atmega328_57600.hex<br /> wget https://proghq.org/media/dupal/dupal_v0.1.2.hex<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_v8.0_atmega328_57600.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> cd ~/dupal<br /> wget https://proghq.org/media/dupal/dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar<br /> <br /> Example output:<br /> <br /> $ java -jar dupal-analyzer-0.1.4-5430dab-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8<br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> nvm compile<br /> sudo nvm install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=881 2022-05-21T21:37:17Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> sudo apt-get install -y avrdude minicom<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> <br /> <br /> ==Building==<br /> <br /> === MCU ===<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program<br /> <br /> === Analyzer ===<br /> <br /> sudo apt install maven<br /> nvm compile<br /> sudo nvm install<br /> <br /> You should now see something like<br /> <br /> $ ls -lah ./target/*.jar<br /> -rw-r--r-- 1 root root 51K May 21 14:34 ./target/dupal-analyzer-0.1.4.jar<br /> -rw-r--r-- 1 root root 536K May 21 14:35 ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar<br /> $ java -jar ./target/dupal-analyzer-0.1.4-jar-with-dependencies.jar -h<br /> [main] INFO info.hkzlab.dupal.analyzer.App - DuPAL Analyzer 0.1.4<br /> [main] ERROR info.hkzlab.dupal.analyzer.App - Wrong number of arguments passed.<br /> dupal_analyzer &lt;serial_port&gt; &lt;pal_type&gt; [&lt;output_file&gt; hex_output_mask]<br /> Where &lt;pal_type&gt; can be:<br /> 10L8<br /> 12H6<br /> 16L8<br /> 20L8<br /> 16R4<br /> 16R6<br /> 16R8<br /> 20R4<br /> 20R6<br /> 20R8</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=880 2022-05-21T21:27:29Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> sudo apt-get install -y avrdude minicom<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 baud using your favorite terminal emulator such as:<br /> <br /> minicom -b 57600 -D /dev/ttyUSB0<br /> <br /> Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go! Press ^A and then x to exit minicom<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=879 2022-05-21T21:25:03Z

<p>Mcmaster: /* Quick start */</p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> sudo apt-get install -y avrdude<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 (ex: screen /dev/ttyUSB0 115200). Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=878 2022-05-21T21:24:54Z

<p>Mcmaster: </p> <hr /> <div>== Quick start ==<br /> You will need:<br /> <br /> * Ubuntu 20.04<br /> * Assembled DuPAL 2.0 w/ 20 pin ZIF installed<br /> ** ATMEGA328P blank / in any state<br /> * DuPAL power supply and USB serial<br /> * avrdude compatible programmer<br /> ** I used avrispmkII<br /> * PAL16L8<br /> * Optional: tool to flash PAL16L8<br /> ** TL866 won't work :(<br /> <br /> ===Quick flash===<br /> <br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Board main page]<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> sudo apt-get install -y avrdude<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 (ex: screen /dev/ttyUSB0 115200). Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> === Quick test ===<br /> For more information see the [https://github.com/DuPAL-PAL-DUmper/DuPAL_Analyzer main page]<br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=877 2022-05-21T07:02:30Z

<p>Mcmaster: </p> <hr /> <div>WIP<br /> ==Quick flash==<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 (ex: screen /dev/ttyUSB0 115200). Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go<br /> <br /> A healthy board should have a steady red power LED and a brief green blink at power on<br /> <br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=876 2022-05-21T06:54:16Z

<p>Mcmaster: /* Quick flash */</p> <hr /> <div>WIP<br /> ==Quick flash==<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> Start up a serial port at 57600 (ex: screen /dev/ttyUSB0 115200). Hit &quot;reset&quot; and you should see:<br /> <br /> (blinky for a few seconds)<br /> <br /> Then:<br /> <br /> DuPAL - 0.1.2<br /> <br /> REMOTE_CONTROL_ENABLED<br /> <br /> If you see this, congrats! your DuPAL is flashed and ready to go<br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=875 2022-05-21T06:50:47Z

<p>Mcmaster: </p> <hr /> <div>WIP<br /> ==Quick flash==<br /> <br /> Pre-compiled hex files: https://proghq.org/media/dupal/<br /> <br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster https://proghq.org/w/index.php?title=DuPAL&diff=874 2022-05-21T06:47:45Z

<p>Mcmaster: </p> <hr /> <div>WIP<br /> <br /> Pre-compiled: https://proghq.org/media/dupal/<br /> <br /> &lt;br /&gt;<br /> <br /> <br /> ==Quick flash==<br /> <br /> ISP connection:<br /> * Pin 1 (red stripe in cable) towards crystal<br /> * Notch faces towards ATMEGA<br /> <br /> You need an avrdude compatible programmer. To see the list of compatible programmers type <br /> <br /> avrdude -c help<br /> <br /> Once you know the flag you need, here's an example assuming avrispmkII:<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -e -u \<br /> -U efuse:w:0xFD:m \<br /> -U hfuse:w:0xDE:m \<br /> -U lfuse:w:0xFF:m \<br /> -U flash:w:optiboot_atmega328.hex<br /> <br /> You should see a green blinky LED<br /> <br /> avrdude -v -c avrispmkII -P usb -p atmega328p -u -D \<br /> -U flash:w:dupal_v0.1.2.hex<br /> <br /> The green blinky might stop. Hit the reset button and it should blink again<br /> <br /> <br /> ==Building==<br /> <br /> Optiboot<br /> <br /> # https://github.com/Optiboot/optiboot<br /> <br /> # 328P uses 115200?<br /> # a few use 57600 but not the one we need :(<br /> # wget https://github.com/Optiboot/optiboot/releases/download/v8.0/Optiboot-8.0.zip<br /> <br /> git clone https://github.com/Optiboot/optiboot.git<br /> cd optiboot<br /> git checkout -b v8.0 v8.0<br /> cd bootloaders/optiboot<br /> make atmega328 AVR_FREQ=20000000L LED_START_FLASHES=8 BAUD_RATE=57600<br /> # sha1sum optiboot_atmega328.hex<br /> # 8a16ce8d98d7bf002c54c7aa911bfd124d9e1961 optiboot_atmega328.hex<br /> <br /> Flash optiboot. Example CLI to use ISP header, but can also put into tl866 etc<br /> <br /> Sample command line:<br /> <br /> [[DuPAL optiboot flash output|Sample output]]<br /> <br /> Originally I tried using BP Microsystems but didn't work (fuses not set right?). I then flashed using avrdude / header and worked (green LED blinking).<br /> <br /> TODO: dump end flash so can program using bp<br /> <br /> cd DuPAL_Firmware<br /> make<br /> make program</div>

Mcmaster