Public
- Public
- Network
- Groups
- Popular
- People

Notices by Mäh W. (maehw@chaos.social)

Mäh W. (maehw@chaos.social)'s status on Friday, 06-Oct-2023 06:46:53 JST Mäh W.
in reply to
- minute
- Dirk Eibach
@de @mntmn it was a little bit hidden, but I found something, indicating that there's flash ID (0x1C), read (0x1B), write (0x1A) and erase (0x19) commands.

In conversation about a year ago from chaos.social permalink
Mäh W. (maehw@chaos.social)'s status on Friday, 06-Oct-2023 06:46:51 JST Mäh W.
in reply to
- minute
- Dirk Eibach
@de @mntmn oh, and you may require to load a flash driver into RAM at the very beginning.

In conversation about a year ago from chaos.social permalink
Mäh W. (maehw@chaos.social)'s status on Friday, 06-Oct-2023 06:46:50 JST Mäh W.
in reply to
- minute
- Dirk Eibach
@de @mntmn Are you familiar with the process? Maybe you could still try the flash ID command without previously loading firmware into RAM. CommandByte=0x1C + Reserved1=0xFF0000 + Reserved2=0x200000. Response should return 0x1C + 2 byte Flash ID. But probably using a UART-based probe and sniffing the protocol messages is more helpful than my random thoughts.

In conversation about a year ago from chaos.social permalink
Mäh W. (maehw@chaos.social)'s status on Friday, 06-Oct-2023 04:23:52 JST Mäh W.
in reply to
- minute
@mntmn no other tools available? 😯

In conversation about a year ago from chaos.social permalink

User actions

👨‍💻 I am interested in wired & radio communication, DSP, (embedded) software dev & engineering, FOSS, reverse engineering, IT security, space, programmable and non-programmable bricks, old and new computer technology, robots & other things. Living in 🇩🇪. Speaking 🇩🇪/🇬🇧/💻 and understanding a little bit of 🇫🇷.

Tags