Tweet
Hello,
I am going to try to collect information about the DEF CON 26 badge, published online, and paste content found online here, with citations for source of information. Almost none of this content is my own. See original data in context by following URL from which data was duplicated.
Comment: I have completed the re-flashing of a badge to the latest firmware (version 2) using Ubuntu and using Windows, and can confirm that process works.
In one case, the upgrade claimed success, but it did not. Re-flashing it again worked.
After flashing, choose "disconnect" in the software, then disconnect the badge, then disconnect power to the badge, then reconnect power to the badge (reboot.)
Content hosted on the DEF CON Media server for this badge: PDF, docs, firmware, more:
URL0 = https://media.defcon.org/DEF%20CON%2026/DEF%20CON%2026%20badge/
URL1 = https://www.reddit.com/r/Defcon/comments/973jik/dc26_official_badge_hardware_ama/
Revised process from my testing:
* Connect your badge to power: most reliable power from my testing was use of a good USB cable to a reliable USB power hub or computer USB port. Maybe try your luck with fresh batteries? You don't want to have low power when flashing firmware.
* If you have properly attached pins 1-5 to your badge and have the PICKit4 attached to a USB port, and then start the "MPLAB X IPE" then it should auto-detect the "Device" and "Tool" and fill those out for you. If no, then you can specify manually:
# Family: 32-bit MCUs (PIC32) (to limit choices for "Device:"
# Device: PIC32MM0256GPM048
# Tool: (Choose wither the PICKit3 or PICKit4, whichever you are using.)
* Hex File (browse to "DEF CON 26 badge by Tymkrs-V2.hex")
* Change speed from "Normal" to "Slow":
# "Setting" menu drop/down, top
# Choose "Advanced Mode"
# Complete password prompt (default password is "microchip")
# Left-side, locate rectangle "Settings" and choose
# Right-side, top "Special Settings" : scroll and look to the far right and find "Program Speed"
# Change "Program Speed" from "Normal" to "Low" (I tested on USB2.0 port, and USB3.0 port, and "normal" speed did not work for me.)
# Locate the tabs, top left "Operate" , "Settings" and choose "Operate"
* If you have not yet connected Pins 1 through 5 to the badge, do that now. Pin1 is closer to the top of the badge. Pin 5 is closest to the bottom of the badge)
* In the MPLAB X IPE application, now find and choose "connect"
# If you see communications complaints in MPLAB X IPE when choosing to connect, re-check and re-connect pins 1-5 to the badge, and try again.
* Once the MPLAB X IPE indicates the connection worked, the grayed-out option "Program" should now be available.
* Choose "Program" to flash new firmware to your badge.
* If you see communication errors at any stage in the "Program" of the badge, re-check pins to badge, reposition, and choose "Program" again.
* It may take a few tries before you find good contact with all 5 pins to all 5 pads on the badge.
* Once you complete the programming of one badge with everything above configured, you can probably remove the pins from that badge, and connect those 5 pins to another badge, and choose the "Program" option again. If the "Program" option becomes grayed-out again, and you want to program more badges, you will need to go back to the "connect" step above, and proceed from there.
Items of caution: be careful with placement of pins. Don't bridge pin-pads on badge when you attach connectors from the PICKit[3||4] to the badge.
Don't let unused pin 6 from PICKit make contact with other leads on the badge.
If you happen to short the badge with the pins, you may harm your badge or your PICKit.
There are some protections inthe PICKit and IPE software to "disconnect" under several circumstances, which include unexpected voltage/current changes.
If you happen to "brick" your PICKit and your PICKit appears to be unresponsive, consider following the procedure suggested on vendor forums:
* QUIT the "MPLAB X IPE" application. Disconnect the PICKit from your USB port. Disconnect 1-6 pins from badge/device. Reconnect the PICKit to a USB port. Launch the "MPLAB X IDE" (IDE not IPE): Locate "Debug" menu drop-down and select, "Hardware Tool Emergency Boot Firmware Recovery" utility, and run this to see if you can "unbrick" your PICKit. (Technically, it wouldn't be bricked if you can recover it, but when in a broken state, where recovery options are not known, "bricked" is an understandable perceived state.)
* If that fails, consider contacting their "CiSAR 'Development Tool Replacement Service Site'": https://www.microchip.com/cisar/Home.aspx
URL2 = https://www.microchip.com/mplab/mplab-x-ide
How do you know which firmware version your badge has? How can you see if you have the latest firmware?
https://twitter.com/wireengineer/sta...19089660485632 and https://twitter.com/wireengineer/sta...19521376051201
Gaining access to the "service menu" is or can be part of the puzzle. You can solve it on your own, or try a search with google or ask other people for how to gain access to it.
I can confirm that once I gained access, I could see a new badge, pre-upgraded, was claiming version "0".
I would expect the version with some fixes distributed are con was version 1.
The latest version in the hexfile on media ( https://media.defcon.org/DEF%20CON%2026/DEF%20CON%2026%20badge/DEF%20CON%2026%20badge%20by%20Tymkrs-V2.hex, with sha256 (of 325bc7ff71f6b5a4c4feb382bc89e326e65092dea5e288c42f 5e00908701db06 DEF CON 26 badge by Tymkrs-V2.hex) flashed a badge up to version 2.
I am going to try to collect information about the DEF CON 26 badge, published online, and paste content found online here, with citations for source of information. Almost none of this content is my own. See original data in context by following URL from which data was duplicated.
Comment: I have completed the re-flashing of a badge to the latest firmware (version 2) using Ubuntu and using Windows, and can confirm that process works.
In one case, the upgrade claimed success, but it did not. Re-flashing it again worked.
After flashing, choose "disconnect" in the software, then disconnect the badge, then disconnect power to the badge, then reconnect power to the badge (reboot.)
Content hosted on the DEF CON Media server for this badge: PDF, docs, firmware, more:
URL0 = https://media.defcon.org/DEF%20CON%2026/DEF%20CON%2026%20badge/
URL1 = https://www.reddit.com/r/Defcon/comments/973jik/dc26_official_badge_hardware_ama/
Originally posted by URL1, Part1
* Connect your badge to power: most reliable power from my testing was use of a good USB cable to a reliable USB power hub or computer USB port. Maybe try your luck with fresh batteries? You don't want to have low power when flashing firmware.
* If you have properly attached pins 1-5 to your badge and have the PICKit4 attached to a USB port, and then start the "MPLAB X IPE" then it should auto-detect the "Device" and "Tool" and fill those out for you. If no, then you can specify manually:
# Family: 32-bit MCUs (PIC32) (to limit choices for "Device:"
# Device: PIC32MM0256GPM048
# Tool: (Choose wither the PICKit3 or PICKit4, whichever you are using.)
* Hex File (browse to "DEF CON 26 badge by Tymkrs-V2.hex")
* Change speed from "Normal" to "Slow":
# "Setting" menu drop/down, top
# Choose "Advanced Mode"
# Complete password prompt (default password is "microchip")
# Left-side, locate rectangle "Settings" and choose
# Right-side, top "Special Settings" : scroll and look to the far right and find "Program Speed"
# Change "Program Speed" from "Normal" to "Low" (I tested on USB2.0 port, and USB3.0 port, and "normal" speed did not work for me.)
# Locate the tabs, top left "Operate" , "Settings" and choose "Operate"
* If you have not yet connected Pins 1 through 5 to the badge, do that now. Pin1 is closer to the top of the badge. Pin 5 is closest to the bottom of the badge)
* In the MPLAB X IPE application, now find and choose "connect"
# If you see communications complaints in MPLAB X IPE when choosing to connect, re-check and re-connect pins 1-5 to the badge, and try again.
* Once the MPLAB X IPE indicates the connection worked, the grayed-out option "Program" should now be available.
* Choose "Program" to flash new firmware to your badge.
* If you see communication errors at any stage in the "Program" of the badge, re-check pins to badge, reposition, and choose "Program" again.
* It may take a few tries before you find good contact with all 5 pins to all 5 pads on the badge.
* Once you complete the programming of one badge with everything above configured, you can probably remove the pins from that badge, and connect those 5 pins to another badge, and choose the "Program" option again. If the "Program" option becomes grayed-out again, and you want to program more badges, you will need to go back to the "connect" step above, and proceed from there.
Items of caution: be careful with placement of pins. Don't bridge pin-pads on badge when you attach connectors from the PICKit[3||4] to the badge.
Don't let unused pin 6 from PICKit make contact with other leads on the badge.
If you happen to short the badge with the pins, you may harm your badge or your PICKit.
There are some protections inthe PICKit and IPE software to "disconnect" under several circumstances, which include unexpected voltage/current changes.
If you happen to "brick" your PICKit and your PICKit appears to be unresponsive, consider following the procedure suggested on vendor forums:
* QUIT the "MPLAB X IPE" application. Disconnect the PICKit from your USB port. Disconnect 1-6 pins from badge/device. Reconnect the PICKit to a USB port. Launch the "MPLAB X IDE" (IDE not IPE): Locate "Debug" menu drop-down and select, "Hardware Tool Emergency Boot Firmware Recovery" utility, and run this to see if you can "unbrick" your PICKit. (Technically, it wouldn't be bricked if you can recover it, but when in a broken state, where recovery options are not known, "bricked" is an understandable perceived state.)
* If that fails, consider contacting their "CiSAR 'Development Tool Replacement Service Site'": https://www.microchip.com/cisar/Home.aspx
URL2 = https://www.microchip.com/mplab/mplab-x-ide
Originally posted by URL2
Originally posted by URL1, Part Terminal Settings
Originally posted by URL1, Wire Service Menu
https://twitter.com/wireengineer/sta...19089660485632 and https://twitter.com/wireengineer/sta...19521376051201
Originally posted by theseURL
I can confirm that once I gained access, I could see a new badge, pre-upgraded, was claiming version "0".
I would expect the version with some fixes distributed are con was version 1.
The latest version in the hexfile on media ( https://media.defcon.org/DEF%20CON%2026/DEF%20CON%2026%20badge/DEF%20CON%2026%20badge%20by%20Tymkrs-V2.hex, with sha256 (of 325bc7ff71f6b5a4c4feb382bc89e326e65092dea5e288c42f 5e00908701db06 DEF CON 26 badge by Tymkrs-V2.hex) flashed a badge up to version 2.