HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hlandau
ortega
C2019–2019
hlandau / ortega

ortega

Ortega FDK

Science & EngineeringHardware & Embedded
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
78GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Ortega FDK

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2019-04-17 07:17:28 UTC to 2019-05-10 04:22:52 UTC.

0122019-04-17 00:00:00 UTC to 2019-04-18 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 172019-04-18 00:00:00 UTC to 2019-04-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-19 00:00:00 UTC to 2019-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-20 00:00:00 UTC to 2019-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-21 00:00:00 UTC to 2019-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-22 00:00:00 UTC to 2019-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-23 00:00:00 UTC to 2019-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-24 00:00:00 UTC to 2019-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-25 00:00:00 UTC to 2019-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-26 00:00:00 UTC to 2019-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-27 00:00:00 UTC to 2019-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-28 00:00:00 UTC to 2019-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 282019-04-29 00:00:00 UTC to 2019-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-30 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-01 00:00:00 UTC to 2019-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-02 00:00:00 UTC to 2019-05-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-03 00:00:00 UTC to 2019-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-04 00:00:00 UTC to 2019-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-05 00:00:00 UTC to 2019-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-06 00:00:00 UTC to 2019-05-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-07 00:00:00 UTC to 2019-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-08 00:00:00 UTC to 2019-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-09 00:00:00 UTC to 2019-05-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-10 00:00:00 UTC to 2019-05-11 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 10

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 172019-04-17 00:00:00 UTC2019-04-18 00:00:00 UTC202
Apr 182019-04-18 00:00:00 UTC2019-04-19 00:00:00 UTC000
Apr 192019-04-19 00:00:00 UTC2019-04-20 00:00:00 UTC000
Apr 202019-04-20 00:00:00 UTC2019-04-21 00:00:00 UTC000
Apr 212019-04-21 00:00:00 UTC2019-04-22 00:00:00 UTC000
Apr 222019-04-22 00:00:00 UTC2019-04-23 00:00:00 UTC000
Apr 232019-04-23 00:00:00 UTC2019-04-24 00:00:00 UTC000
Apr 242019-04-24 00:00:00 UTC2019-04-25 00:00:00 UTC000
Apr 252019-04-25 00:00:00 UTC2019-04-26 00:00:00 UTC000
Apr 262019-04-26 00:00:00 UTC2019-04-27 00:00:00 UTC000
Apr 272019-04-27 00:00:00 UTC2019-04-28 00:00:00 UTC000
Apr 282019-04-28 00:00:00 UTC2019-04-29 00:00:00 UTC000
Apr 292019-04-29 00:00:00 UTC2019-04-30 00:00:00 UTC000
Apr 302019-04-30 00:00:00 UTC2019-05-01 00:00:00 UTC000
May 12019-05-01 00:00:00 UTC2019-05-02 00:00:00 UTC000
May 22019-05-02 00:00:00 UTC2019-05-03 00:00:00 UTC000
May 32019-05-03 00:00:00 UTC2019-05-04 00:00:00 UTC000
May 42019-05-04 00:00:00 UTC2019-05-05 00:00:00 UTC000
May 52019-05-05 00:00:00 UTC2019-05-06 00:00:00 UTC000
May 62019-05-06 00:00:00 UTC2019-05-07 00:00:00 UTC000
May 72019-05-07 00:00:00 UTC2019-05-08 00:00:00 UTC000
May 82019-05-08 00:00:00 UTC2019-05-09 00:00:00 UTC000
May 92019-05-09 00:00:00 UTC2019-05-10 00:00:00 UTC000
May 102019-05-10 00:00:00 UTC2019-05-11 00:00:00 UTC101

What Hacker News says

3 sources
hlandau·Apr 17, 2019
There weren't that many off-the-shelf tools involved, other than things like binwalk and disassemblers. My workflow can also be hilariously ghetto at times: I like to output hexdump -C to a file, then annotate that in vim. For example: https://github.com/hlandau/ortega/blob/master/notes/bcm5719_... Lots of tools were written from scratch. I wrote otgdbg for probing the device; this program has tons of subcommands to let me manipulate the device in various ways, get/set registers, boot a program on the MIPS side from memory, boot a program on the APE side from memory, copy a new image to flash, etc. otgimg examines firmware images and prints information about them, like the MAC addresses in the configuration block, etc. apeimg shows information about APE firmware images and can decompress them. Since the image formats are custom, I had to
Read the rest
use linker scripts to build the images, but some fixups could only be done programmatically, like calculating CRC fields. These fixups were done with small C programs which the build system runs afterwards. The APE used a more sophisticated image format with section headers, etc. The fixup program for the APE had to compress some of the sections, etc. before setting the CRCs. These tools are all available in the repository, but most of them link to small amounts of proprietary/reversed code which is automatically scrubbed from the public release. It's not a large amount of code which would need to be replaced, though, if someone wants a tool like otgdbg to probe Broadcom NICs in arbitrary ways. Oh, I should also mention that using clang and lld rather than gcc/binutils made targeting different architectures a breeze. It's long been a bone of irritation to me that you have to recompile gcc to retarget it; with clang, I could target both MIPS and ARM without compiling a new toolchain. https://github.com/hlandau/ortega/blob/master/cc_mips https://github.com/hlandau/ortega/blob/master/cc_arm
In Adventures in reverse engineering Broadcom NIC firmware

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.