imem | imem 是important和emergent的开头两个字母

RISC-V deals with everything in byte addresses (from page 19 of the ISA manual: "RV32I provides a 32-bit user address space that is byte-addressed and little-endian"). So when using byte addresses, it makes sense to think of the PC as incrementing by 4, as each of the RV32 instructions are 4 bytes.

When we say RISC-V increments the PC by 4, what that means is that for any given byte address X of a 32-bit RISC-V instruction, the next instruction will begin in memory at address X+4. (Note that when using compressed instructions, which are 16 bits / 2 bytes, the PC is incremented by 2).

An IMEM read width of 16 bits means 2 reads from IMEM are necessary to get a full instruction, and an IMEM read width of 32 bits means only 1 read from IMEM is necessary to get a full instruction. But these are implementation considerations, not an ISA considerations -- you could hypothetically implement an ISA-compliant RISC-V processor with either type of IMEM.

First, you have an extra u200b character. And second, you can use setTimeout function.

Disclaimer: I'm not a Tcl expert, so there's probably a more optimized solution out there.

There's a command called examine that you can use to get the value of obejcts.

I created a similar testbench here with a 256 x 32 array, the results were

explain this “Addresses are for individual bytes (8 bits)” for me?

It means that size of a byte is 8 bits. Two adjacent addresses will be 8 bits apart. A 32 bit word consists of 4 bytes.

Furthermore it means that - even though address operands of instructions must be aligned to a 4 byte boundary as explained in the following sentence - each byte has a unique address.

By unique address, do you mean unique 5 bit values?

No. The memory addresses are 32 bit values.

where are addresses usually saved?

Where-ever any values are saved. In the given description, two possible places have been described: In memory, or in a register.

Your using statement will make sure that the stream gets closed and therefore flushed automatically. Unfortunately you retrieve the ciphertext / plaintext from the MemoryStream before that.

Don't use PasswordDeriveBytes, especially not for more than 20 bytes, it's insecure. Rather use `Rfc2898DeriveBytes.