Talk:Boot ROM

This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science articles

Low

This article has been rated as Low-importance on the project's importance scale.

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

No all boot ROMs are mask ROM

I've replaced reference to MASK ROM by more generic "ROM" since some implementations of boot ROMs aren't masked ROMs at all. E.g. most STM32 chips provide boot ROM but it isn't really masked - it seems to be flashed by STMicro on fab using hardware interfaces into dedicated flash array area known as "system memory", which set readonly after initial programming. From user's standpoint it's a "boot ROM" and can't be distinguished from any other boot ROM. However underlying technology isn't mask-based, more like custom flash controller operations and locking some flash memory read-only. User could also arrange similar sequence on part of user-supplied firmware as well, forcing some flash area read-only, effectively creating user-supplied boot ROM equivalent used to update firmware.

Additionally I've added description of STM32 booting and how it interacts with boot ROM in this particular case based on my experience and STMicro appnotes and datasheets.

Does this include BIOS ROMs, UEFI ROMs, Open Firmware ROMs, etc.?

I.e., does this include ROMs that can boot the system, but also have their own user interface to perform other functions, such as providing services to boot loaders or operating systems, and configuration? The examples given seem largely to be for embedded systems and devices such as smartphones rather than desktop/laptop computers and servers. Guy Harris (talk) 07:26, 25 September 2024 (UTC)[reply]