2023-12-04 09:56 AM
Hi, I have a custom board with a stm32mp153. I was able to get past the trusted bootloader and into optee. It builds the mmu map and then panics when checking it. I am able to partially step through building the table and the memory starts to get corrupted but I can't see why. I also have a 157-ev which works fine when I build for that on the same dev machine. I am looking for possible clues on where to go from here.
Solved! Go to Solution.
2023-12-08 12:05 AM
Hi @dkal
if you are writing to DDR, maybe double check the correct DM Vs DQ/DQS wirings on your schematics. We had seen similar behavior when customers swapped Data Mask and Bytes which mean x32-bits write works but not bytes.
Regards.
2023-12-04 01:56 PM
I've tracked the issue down to memmove not working properly, why would it be fine in stm32mp157 and not fine in stm32mp153?
2023-12-04 05:49 PM
More specifically, the memmove is filling the destination with garbage even though the source and destination pointers are valid.
2023-12-05 08:06 PM
It seems that single byte copies are the issue, when it can do a more optimized copy with longs, that memory is correct.
2023-12-07 08:20 AM
I am going to assume that this is a RAM issue and am now trying the DDR utility.
2023-12-08 12:05 AM
Hi @dkal
if you are writing to DDR, maybe double check the correct DM Vs DQ/DQS wirings on your schematics. We had seen similar behavior when customers swapped Data Mask and Bytes which mean x32-bits write works but not bytes.
Regards.
2023-12-08 11:25 AM
Thank you, we will check.
2023-12-08 01:18 PM
We have
DDR_DQM0 connected to UDM
DDR_DQM1 connected to LDM
Hardware guys said they did it that way because thats how the eval board is connected, it looks that way in the schematic, is this correct?
2023-12-08 02:49 PM
Oh the DQM0 and DQS0 are not consistent with upper and lower.