Mateusz Hołenko

Thanks @amr-25 for reporting the issue, we'll look into it.

Hi @andresdemski, that's an interesting topic. At the moment automatic endianness translation can be achieved by marking peripheral models with [the atrribute](https://github.com/renode/renode-infrastructure/blob/master/src/Emulator/Main/Peripherals/EndianessAttribute.cs) (which I assume it's what you've already tried)....

I guess that linked tasks/PRs provide all the status - we didn't work on the LTO issue lately. As described in #253, using it with optimisations caused problems back in...

@DurandA No, I don't recall that error. Our problem was that the linker couldn't find one of the functions that was a part of the code - it looked like...

@michalsieron will take a look at that

Added my comments to #1287

Hi @katyo, thanks for reporting the issue! Indeed https://github.com/renode/renode-infrastructure/blob/c6f3af35c129d58e1e20779a81521663878f1940/src/Emulator/Peripherals/Peripherals/Network/SynopsysEthernetMAC.cs#L198 looks quite suspicious - it looks that the model doesn't accept any incoming frames until the first one is sent. I'm...

Unfortunately I was not able to reproduce the problem - unhandled read/write logs are decorated with the CPU name and PC when the access it made from the CPU thread...

Hi @xobs, in 94083f21499b74de47df51038e1f2b08fd8b4f1 we introduced a mechanism for handling exceptions on the C#/C boundaries - those `_ex` functions are part of it. Although they are not explicitly visible in...

We checked this and it seems to be related to the toolchain itself. Following your instructions, but using Visual Studio 2019 build tools, *without* replacing v4.5 to v4.8 we were...