easy 10 pts Solved

16-Bit Endianness Swapper

Swap the byte order of a 16-bit word — the wiring fix needed whenever two datapaths disagree on big-endian vs little-endian byte order.

Verilog problems / Combinational Design

What you must build

Swap the byte order of a 16-bit word — the wiring fix needed whenever two datapaths disagree on big-endian vs little-endian byte order.

Engineers use “16-Bit Endianness Swapper” as a building block in combinational design. Interviewers ask for the same ports and the same corner cases this judge covers. Completing it in the browser is the same skill as writing synthesizable RTL at work, minus the EDA license.

Concept: Endianness swapping is pure rewiring, not arithmetic: move the low byte to the high position and vice versa with {word_in[7:0], word_in[15:8]}. It's an easy copy-paste trap to instead write the bytes back in their original order ({word_in[15:8], word_in[7:0]}), which silently compiles and simulates as a no-op.

Port contract

The judge instantiates exactly these ports. Extra ports or a different module name fail to elaborate.

NameDirWidthDescription
word_ininput16Input word
word_outoutput16word_in with its two bytes swapped

How to approach this kata

This is an introductory kata. Prefer a clear continuous assignment or a small combinational always block. Name the module top_module and keep the port list identical to the table — the hidden testbench instantiates that name.

Hidden tests instantiate top_module, drive the ports, and compare every sample against a golden model. They do not grade coding style. They do grade X/Z, off-by-one counters, and ignoring enables. Sign in only when you want the run saved on the leaderboard — the specification below is public.

Starter shape

Copy this skeleton into the editor (or press Reset starter). Fill the body; do not rename the module.

module top_module(
  input  [15:0] word_in,
  output [15:0] word_out
);

  // Your code here — word_out = {low_byte, high_byte}.

endmodule

Why this shows up in interviews

16-Bit Endianness Swapper sits under Combinational Design (combinational, datapath). Concept: Endianness swapping is pure rewiring, not arithmetic: move the low byte to the high position and vice versa with {word_in[7:0], word_in[15:8]} . It's an easy copy-paste trap to instead write the bytes back in their original order ( {word_in[15:8], word_in[7:0]} ), which silently compiles and simulates as a no-op.

A passing solution is synthesizable intent: no delays in the DUT, no initial blocks inside top_module, and no reference to testbench tasks. Use blocking assignments only in combinational always blocks; use non-blocking for registers clocked by clk.

Related problems

  • 2-to-1 Multiplexer — Select between two 1-bit inputs using sel. When sel=0 output a; when sel=1 output b.
  • 1-Bit Full Adder — Compute sum and carry-out for a + b + cin.
  • 4-to-1 Multiplexer — Select one of four 1-bit inputs using a 2-bit sel. sel=00→in0, 01→in1, 10→in2, 11→in3.
  • 4-to-2 Priority Encoder — Output the index of the highest-priority (MSB-most) set bit in a 4-bit input, plus a valid flag when any bit is set.

FAQ

What does this problem require?

What does the 16-Bit Endianness Swapper problem ask for? Swap the byte order of a 16-bit word — the wiring fix needed whenever two datapaths disagree on big-endian vs little-endian byte order. Implement it as Verilog module top_module with the listed ports.

Combinational or sequential?

Is 16-Bit Endianness Swapper combinational or sequential? Tags: combinational, datapath. Follow the clock/reset ports if they appear in the table; if there is no clock, use continuous assignment or combinational always @(*).

How does the auto-grader work?

How is 16-Bit Endianness Swapper graded? A hidden SystemVerilog/Verilog testbench in the EcrioniX judge simulates your module in the browser. You pass when every directed vector matches, including the waveform contract shown on this page.

Write a module named top_module matching the ports below exactly.
Expected waveform
Your solution
Judge output
// Output appears after you run tests.