Building A Custom Zynq-7000 SoC Development Board From The Ground Up

I have a new post on Hackaday: Building A Custom Zynq-7000 SoC Development Board From The Ground Up.

The presenter starts by designing the power system, then makes progress on power, improves the schematic, integrates DDR RAM, adds USB PHY, Ethernet PHY, and SD card, starts on HDMI, makes progress on layout, makes progress on routing, continues with routing, configures with Vivado and estimates costs, receives PCBs and components, starts the PCB assembly, adds power rail components, adds core components, connects power and does initial programming, makes an LED blink, gets the ARM APU working, troubleshoots FT2232H to JTAG, resolves FT2232H to JTAG issue, adds UART and DDR, gets HDMI working, installs PetaLinux, and at long last configures USB and Ethernet in PetaLinux.

See AMD Zynq 7000 SoCs for specs from AMD. The executive summary is that this SoC includes an ARM Cortex-A9 Based APU and an Artix-7 FPGA (or a Kintex-7 FPGA on higher models). We suppose this is an opportune time to mention that in case you missed it Xilinx was recently acquired by AMD which is why you see the AMD branding now.

Summarizing references from these videos, other videos include What your Differential Pairs Wish You Knew and How to Achieve Proper Grounding by [Rick Hartley]; books referenced include Printed Circuits Handbook 7ed and Signal and Power Integrity Simplified 3ed; courses referenced include Mixed-Signal Hardware Design with KiCad and Advanced Digital Hardware Design from [Philip Salmony]; and software used includes EasyEDA, Vivado, Vitis IDE, and Tera Term.

New Zealand’s $16 Billion Public Health System Runs on a Single Excel Sheet

This is a note for Future John: New Zealand’s $16 Billion Public Health System Runs on a Single Excel Sheet.

From the report:

Notably, one major issue was through a significant reliance on the use of an Excel file to manage the consolidated financials of the organisation. This spreadsheet was the primary data file used by HNZ to manage its financial performance. It consolidated files from each district into a single spreadsheet, and key reports, such as the monthly finance report, were produced from it. The use of an Excel spreadsheet file to track and report financial performance for a $28bn expenditure organisation raises significant concerns, particularly when other more appropriate systems are present on the IT landscape.

This Excel file is flawed in that:

  • Financial information was often ‘hard-coded,’ making it difficult to trace to the source or have updated data flow through.
  • Errors such as incorrectly releasing accruals or double-up releases were not picked up until following periods.
  • Changes to prior periods and FTE errors in district financial reporting Excel submissions, would not flow through to consolidated file.
  • The spreadsheet can be easy to manipulate information as there is limited tracking to source information where information is not flowing directly from accounting systems.
  • It is highly prone to human error, such as accidental typing of a number or omission of a zero.

The cumbersome process of collecting data also meant monthly financial reporting usually took 12-15 days to consolidate and 5 days to analyse. Adding to that the time associated with the creation of the monthly finance reports and circulation of these to the Board, there was an inevitable challenge of obtaining real-time financial information from one source of truth.

Voyager bug fix

This is too cool. A core dump then binary patch to work around memory hardware failure 15 BILLION MILES AWAY: How NASA Fixed a Software Bug 15 BILLION MILES AWAY | Voyager 1