charcoal141

charcoal141 / Map-View

Public

Interactive treemap visualization for embedded `.map` files — see where your firmware memory and flash goes at a glance. 嵌入式 `.map` 文件的交互式 Treemap 可视化工具 — 一眼看清固件内存和flash分布。

13
3
89% credibility
Found May 25, 2026 at 13 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
TypeScript
AI Summary

Map View is a VS Code extension that transforms cryptic memory report files from embedded firmware builds into beautiful, interactive treemap visualizations. It supports multiple compiler toolchains (Keil MDK for ARM chips, GCC for various architectures, ESP-IDF for Espressif chips, and ArtInChip for RISC-V) and displays memory usage as color-coded blocks—blue for code, green for read-only data, orange for read-write data, and red for zero-initialized data. Users can click to explore modules in detail, search for specific functions, and configure their actual chip memory sizes to see accurate percentage usage. The tool helps embedded developers quickly understand where their limited flash and RAM is being consumed across their own code, third-party libraries, and system components.

How It Works

1
💾 You're building firmware for a tiny computer

You're working on an embedded project like an ESP32 temperature sensor or STM32 robot controller, and you need to see where all your memory is being used.

2
🔍 You find a mysterious .map file

When you compile your code, your compiler spits out a detailed memory report file that lists every function, variable, and library taking up space in your chip.

3
📦 You install Map View in VS Code

You search for 'Map View Embedded' in the VS Code marketplace and install it with one click—it takes just seconds to add to your editor.

4
🗺️ You open your memory map and see a colorful picture

Right-click your .map file and choose 'Open Map View'—instantly, a beautiful treemap appears showing your entire memory as colored blocks sized by how much space each piece takes.

5
You explore your memory in two ways
📍
Region View

See your memory organized by where it's stored—your code in flash, your variables in RAM, with clear totals for each.

📁
Module View

See your memory organized by which parts of your project use it—your own code, third-party libraries, system components.

6
👆 You click to drill down into details

Hover over any block to see its size and address, then click to zoom in and see the individual functions and sections inside.

7
🔦 You search for anything specific

Type in the search box to instantly highlight a function or module across your entire visualization—no more scrolling through walls of text.

✅ You understand your memory footprint at a glance

With colorful blocks, clear percentages, and easy navigation, you can finally see exactly where your firmware's memory is going and make smart decisions about optimization.

Sign up to see the full architecture

6 more

Sign Up Free

Star Growth

See how this repo grew from 13 to 13 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is Map-View?

Map-View is a VS Code extension that turns cryptic linker map files into interactive treemap visualizations. You open a `.map` file, and instead of scrolling through thousands of lines of hex addresses and section names, you get a color-coded heatmap showing exactly where your firmware's ROM and RAM is going. Click any block to drill down into individual modules, functions, and sections. It parses output from Keil MDK, GCC/GNU ld, ESP-IDF, and ArtInChip toolchains, so if you're working on STM32, ESP32, or RISC-V embedded projects, this handles your build system.

Why is it gaining traction?

Embedded developers have always struggled with memory optimization. The standard approach involves grepping through dense text files or using vendor-provided tools that feel like they were built in 2005. Map-View changes this by bringing modern data visualization to an old problem. The treemap makes it immediately obvious which libraries or modules are eating your flash. You can search across the entire map, configure your actual chip memory sizes to see real percentages, and navigate between Region View and Module View depending on how you think about your memory layout.

Who should use this?

Firmware engineers working on resource-constrained embedded systems. If you're optimizing an ESP32 project and wondering why your flash is almost full, or debugging a STM32 build where RAM keeps overflowing, this gives you instant visual feedback. Embedded developers who maintain multiple projects with different toolchains will appreciate the multi-format support. Hobbyists building on ESP-IDF will find it especially useful for understanding what the IDF framework costs in memory.

Verdict

This is a genuinely useful tool for a specific niche, and the implementation is clean with zero runtime dependencies. However, the 0.8999999761581421% credibility score and 13 stars reflect a very young project with limited community validation. Test coverage and documentation are minimal. Worth installing if you regularly work with map files, but treat it as a helpful utility rather than production-grade infrastructure.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.