Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Loading fails for nanox #28

Open
polarker opened this issue Aug 28, 2023 · 4 comments
Open

Loading fails for nanox #28

polarker opened this issue Aug 28, 2023 · 4 comments

Comments

@polarker
Copy link

I got Invalid status 6512 without "apiLevel": 1. Then got Invalid status 511f (Unknown reason) with "apiLevel": 1.

What could be the root cause of 511f?

Here is the Manifest:

{
  "binary": "nanox.hex",
  "apiLevel": "1",
  "dataSize": 0,
  "derivationPath": {
    "curves": [
      "secp256k1"
    ],
    "paths": [
      "m/44'/1234'"
    ]
  },
  "flags": "0x200",
  "icon": "alph_14x14.gif",
  "name": "Alephium",
  "targetId": "0x33000004",
  "version": "0.2.0"
}
@polarker
Copy link
Author

@yhql Is the apiLevel supposed to be 1 for nanox?

@yhql
Copy link
Contributor

yhql commented Aug 29, 2023

Hi, sideloading apps is unfortunately not possible on Nano X. Recommended way of testing for now is using speculos

@polarker
Copy link
Author

Hi, sideloading apps is unfortunately not possible on Nano X. Recommended way of testing for now is using speculos

It seems to work well with apiLevel = 5. What's the meaning of such api levels?

@yhql
Copy link
Contributor

yhql commented Sep 5, 2023

the api levels represent the OS's version, more or less. A change in api level means that some syscall changed in behaviour.
Current api_level of Nano X is indeed 5, but now this value is injected by the SDK itself at compile time, you don't need to specify it in your app's Cargo.toml anymore

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants