Did you ever found firmwares for Tricore or v850 architectures accessing addresses starting with 0xa.. instead of the 0x80.. one? after so much research I end up learning that this is handled by the mmu which applies a cache layer on top of the same memory range. In other words: IDA lies by fake the references by dropping the 3rd bit, ghidra can't handle this, and r2 is again the only tool able to properly define this memory layout.
https://community.infineon.com/t5/AURIX/About-the-issue-with-lsl-files/td-p/676113#.
pancake :verified: /
npub1en…6wye5
2024-08-31 14:30:10
Author Public Key
npub1en9zfs08erwfq69scrmw6wr8pkv46skxl8k4lhx8yka2pcua5xnq26wye5Published at
2024-08-31 14:30:10Event JSON
{
"id": "8de883c02fe2babc563fb6c8732e076e42ab0321b968726b9e1d5c45dead29be",
"pubkey": "ccca24c1e7c8dc9068b0c0f6ed38670d995d42c6f9ed5fdcc725baa0e39da1a6",
"created_at": 1725114610,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@pancake/113057111110829672",
"web"
],
[
"proxy",
"https://infosec.exchange/users/pancake/statuses/113057111110829672",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/pancake/statuses/113057111110829672",
"pink.momostr"
],
[
"-"
]
],
"content": "Did you ever found firmwares for Tricore or v850 architectures accessing addresses starting with 0xa.. instead of the 0x80.. one? after so much research I end up learning that this is handled by the mmu which applies a cache layer on top of the same memory range. In other words: IDA lies by fake the references by dropping the 3rd bit, ghidra can't handle this, and r2 is again the only tool able to properly define this memory layout.\n\nhttps://community.infineon.com/t5/AURIX/About-the-issue-with-lsl-files/td-p/676113#.",
"sig": "aadf2a99b8ff29ad6119dc0585988172b52b7de96e0660ba7935844a392e12348a4df23645dc3c1200731bcd23b909e886718e2bc4e66e92034e628da883b85c"
}