A request that names R5F562T6ADFK#13 has already answered three of the five questions a quotation needs, provided somebody reads the string correctly. It is not a single identifier. It is a Renesas ordering code: a prefix, a group, a memory class, a variant letter, a package code, and after the hash a version code. Each field settles something different, and the only field that says nothing about the silicon is the one after the hash.

That last point is the one worth stating early, because it is where bills of materials and datasheets part company. The #13 does not name a different chip. It names a shipping and qualification configuration, and a customer who believes that #13 and #V3 are different devices will ask for two quotations where one would do.

The device itself is an RX62T group part: a 32-bit RX core running to 100 MHz, with a single-precision floating-point unit, a five-stage pipeline specified at 1.65 DMIPS per megahertz, and a peripheral set aimed squarely at motor control — two twelve-bit converter units, a six-channel motor-control timer, a thirty-two-bit general timer, a port output enable block for inverter drives, plus CAN, serial and synchronous serial channels.

The code, decoded

Three rows do real work in a quotation. The group decides the architecture and therefore the disassembler. The memory class decides how long the image should be, which is the first check on any read. The package decides whether the job is a bench exercise or a laboratory one.

The version code does none of that, and it is the row people argue about.

What the memory digit changes and what it does not

Across the group, flash is offered in two sizes and the RAM figure is fixed. The instruction set is identical in both, and so is the peripheral map. That produces one asymmetry that matters commercially: an image taken from the smaller member will run on the larger one, because every address it uses exists. An image taken from the larger member will not run on the smaller one, because the top of the map is simply absent.

This is why the memory class belongs in the first reply rather than in the final report. A customer who wants a replacement built has to be told which member the recovered image assumes, or the replacement will be ordered in the wrong size and will fail at the first jump into a region that does not exist.

The image length is also the cheapest integrity check available. If the read returns fewer bytes than the class implies, the tool truncated. If it returns more, the device profile was set to a larger member and the extra bytes are fiction. Neither condition needs a datasheet to detect.

Why “software” is the most expensive of the eight deliverables

The original page used the word software, and of the eight nouns this site’s pages use — software, program, code, binary, heximal, flash, EEPROM, firmware — software is the one with the widest meaning and the largest cost range.

A binary is the array as bytes. A heximal is the same array in a container with addresses. A program is a bundle that a production line can burn. Software implies something a person can read, modify and rebuild.

On this device that means four passes beyond the read. The vector table has to be mapped, because RX keeps its reset and exception vectors at the very top of the address space rather than at zero, and a listing that ignores that reads as a program with no entry point. The option-setting memory has to be decoded, because it holds the watchdog and protection configuration and its bit layout is not obvious from a hex dump. The peripheral initialisation sequence has to be identified, because on a motor-control part every timer and converter is configured in the first few hundred instructions and the rest of the code means nothing without it. And the constant pools have to be separated from code, because a 32-bit CISC core with variable-length instructions embeds literals inside the instruction stream.

What does not come back is equally specific: function and variable names, comments, macros, the original compiler’s inlining decisions, and the distinction between two source statements that produced the same instructions. A delivery that promises those is promising something no read can supply.

Three artefacts that must travel with the source

A source-level delivery on this part is only usable with three companions, and each one is a file rather than a paragraph.

A vector map, listing each exception and interrupt vector with the address it points at and the peripheral it belongs to. Without it, a maintenance engineer changing one routine cannot tell which entry point calls it.

An option-byte record, with the watchdog configuration, the protection state and the reset behaviour stated in words rather than as a hex value.

A peripheral ownership table: which timer channel drives which pin, which converter unit samples which input, which serial port talks to what. This is reconstructable from the initialisation code and it is the single most useful thing a recovery can produce for a customer who intends to keep the product alive, because it is the part of the design that is documented nowhere else.

The scope question that saves a week

Two customers asking for software want different projects, and the question that separates them is whether the deliverable is meant to be rebuilt or modified.

A rebuild needs a byte-accurate image, the option bytes, and enough structure to confirm the image is complete. That is a week of work on a part this size.

A modification needs everything above plus readable control flow, named data regions, and an explanation of the timing constants. That is several weeks, and the estimate depends on how much floating-point code the design contains — an FPU-heavy motor control loop with tuned coefficients is a very different proposition from a serial gateway.

Asking that question before quoting is worth more than any technical refinement in the proposal, because it changes the number by a factor of five.

For the sibling order code where the same group is quoted under a different version suffix, R5F562T6EDFF program reversal continues with the boot-mode route. For the same deliverable on a smaller array, R5F562T6BDFF software takes the source-reconstruction view. And for a Renesas part of an earlier generation, where the flash controller behaves quite differently, R8C R5F212B7SNFP flash copying is the useful comparison.

FAQ

Does the #13 change the die? No. It is a shipping and qualification configuration. The group, memory class and package fields name the silicon; the version code names the paperwork.

Can software be delivered without the option bytes? It can be delivered, and it will not rebuild correctly. The watchdog and protection configuration lives there, and a rebuilt unit with a different configuration behaves differently from the original under fault conditions.

Is a 32-bit image harder to verify than an 8-bit one? Easier in one respect and harder in another. The image is longer, but the vector table at the top of the map and the fixed exception entries give a strong structural check that small parts do not have.

The short version

Read the ordering code before the die: group for the architecture, memory class for the expected length, package for the access route, and the hash suffix for nothing that affects silicon. Then decide whether software means rebuild or modify, because that word covers a factor of five in cost. Everything else on this part follows from those two decisions.

Comments are closed.