Endianness problem on iOS
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 35
- Forks
- 48
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 7
Description
On iOS, there seems to be an endianness problem of some kind...
Loading the correct 1.02 US TOS image (md5 c1c57ce48e8ee4135885cee9e63a68a2) throws an error :
Your TOS image seems not to be a valid file!
(TOS version 201, address $fc00)
I can't go any further and check if it does recognize disks correctly after that...
(iOS 12.1.2 - arm64)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on iOS 12.1.2/arm64 with the specified 1.02 US TOS image and its given MD5. Trace the TOS validation path and compare the iOS result with a working platform, focusing on the reported endianness issue. Done means the image is accepted on iOS and disk recognition can be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ios
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100