What Happens To Football Gaming History After John Madden Passes Away

Explicit content warning

01/04/22 • 8 min

Link to article: https://bit.ly/3zEnP78
Legendary coach and broadcaster John Madden died Tuesday morning, the NFL announced. For fans, no one is more synonymous with football than Madden, and perhaps no one person has done more to bring new people into the game.
“On behalf of the entire NFL family, we extend our condolences to Virginia, Mike, Joe and their families,” NFL Commissioner Roger Goodell said in an official statement. “We all know him as the Hall of Fame coach of the Oakland Raiders and broadcaster who worked for every major network, but more than anything, he was a devoted husband, father and grandfather.
“Nobody loved football more than Coach. He was football. He was an incredible sounding board to me and so many others. There will never be another John Madden, and we will forever be indebted to him for all he did to make football and the NFL what it is today.”
A late draft pick, Madden’s NFL stint was set to start in 1958 with the Philadelphia Eagles, but a career-ending knee injury sidelined him before his professional gridiron days started. Madden moved into coaching, beginning at a community college. He ended up in Oakland, bringing home a Lombardi Trophy and becoming the winningest coach in Raiders history. Madden had secured his spot as one of the greatest coaches of his era before stepping down to become a broadcaster. On TV, Madden excelled as well, becoming one of the most memorable and enjoyable color commenters. He won 16 Emmy Awards before retiring in 2008.

Support the show

Send us a text

Support the show

Previous Episode

Ubisoft Doubles Down with Ubisoft Quartz and Believes It Is The Future

Send us a text

Link to article: https://bit.ly/3qIWts7
Ubisoft’s entry into the maelstrom of NFTs, which has so far been comically inept, has also been received by the wider public with an enormous amount of outright hostility. And how has the company responded to this backlash? Exactly as you would expect.
While some studios dipped their toes into the water, found their fanbases were not exactly thrilled with the prospect, and bailed, Ubisoft is far too invested in this bullshit to go backing out now. And so, in an interview with a crypto news site, the company has instead explained how they intend on ignoring your concerns and pushing right on ahead with everything.
We have received a lot of feedback since the announcement, and we hear both the encouragement and the concerns. We understand where the sentiment towards the technology comes from, and we need to keep taking it into consideration every step of the way.

Support the show

Next Episode

HWFLY Modchips Can Now Be Flashed and Used on Nintendo Switch Consoles

Send us a text

Link to article: https://bit.ly/3nRtQbZ
IF YOU BREAK YOUR BOOT0 PIN. DO NOT DM ME ASKING FOR HELP. THAT'S IT. YOU BREAK THAT PIN AND YOU CANT FLASH. YOUR CHIP IS STUCK WITH WHATEVER HWFLY PUT ON IT
Pre-requisites:
Raspberry Pi Zero W
You may use another flasher if you desire.
Pinout Diagram
Modchip Diagram
FULL_CHIP_STOCK.bin
Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.
Solder a wire to each of the following pinouts on the Raspberry Pi Zero W:
3.3V
Ground
GPIO 14 (UART TX)
GPIO 15 (UART RX)
Do the following to prepare the modchip:
Lift pin 44 (also known as BOOT0).
You will need a way to power the chip, so you need to find two 3.3v points. It can be on a MOSFET, but it will differ based on the revision of the modchip.
Connect Ground on your Raspberry Pi Zero W to the Ground pin on your modchip.
Check the Modchip Diagram, find the PA9(TX) and the PA10(RX) pins on your modchip, and do the following:
Connect GPIO14(TX) on your Raspberry Pi Zero W to the PA10(RX) pin on your modchip.
Connect GPIO15(RX) on your Raspberry Pi Zero W to the PA9(TX) pin on your modchip.
Boot your Raspberry Pi Zero W and do the following:
In the terminal, type the following command, and press enter:
Bash:
sudo nano /boot/config.txt
Add the following line to the end of the file:
INI:
dtoverlay=pi3-miniuart-bt
Press CTRL + X to save and exit the editor.
In the terminal, type the following command, and press enter:
Bash:
sudo nano /boot/cmdline.txt
Remove the following line from the file:
INI:
console=serial0,115200
Press CTRL + X to save and exit the editor.
Restart your Raspberry Pi with this command
Bash:
sudo /sbin/reboot
In the terminal, type the following commands, and press enter after each command:
Bash:
git clone https://github.com/Pheeeeenom/stm32flash.git
cd stm32flash
sudo make install
Now you will flash the modchip.
Note: This will remove read protection, and the modchip will wipe itself (that is what we want).
In the terminal, type the following command, and press enter:
Bash:
stm32flash -k /dev/serial0
Now to flash Spacecraft-NX Version 0.2.0, type the following, and press enter:
Bash:
stm32flash -v -w ./FULL_CHIP_STOCK.bin /dev/serial0
Once you're done flashing your modchip, remove the wiring from the modchip, and restore the 3.3v pin on the modchip to its original position.
Please post pictures of your work here to further the identification of the different board revisions!
UPDATE: So it seems like stitching the spacecraft bootloader and firmware together from the repo causes unstable glitching behaviors. For now, consistent glitching behavior works with this bootload/firmware combo. This is the original file on the OLED variant chip which has 0.2.0 spacecraft. As for glitching, I'll figure it out, give me some time...unless someone else wants to hop in and reverse the differences.
For now, this at least solves the 0.1.0 HWFLY gen 3 issue. More to come.
UPDATE 2: This is only going to work on some HWFLY chips. Older ones use higher protection than the new revisions that seem to use the QFN FPGA. here