Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command-line UI is highly confusing #2

Open
pfalcon opened this issue Nov 16, 2014 · 5 comments
Open

Command-line UI is highly confusing #2

pfalcon opened this issue Nov 16, 2014 · 5 comments

Comments

@pfalcon
Copy link
Contributor

pfalcon commented Nov 16, 2014

I flashed frankenstein firmware yesterday and couldn't do anything useful to it, I thought almost no functions are implemented. Only after checking forum thread it turned out something really works. So, let's go over confusing stuff:

  1. iwconnect doesn't say anything, so it doesn't seem to work. It's nowhere clear that ifconfig should be used after it to check status. So, iwconnect should say "ok" or "fail" (detailed error message, of course).
  2. It's nowhere clear that changes done by iwconnect/iwmode may not be applied immediately, but require reset. Again, it should say when it's the case.
  3. Nowhere clear that spi_dump requires decimal numbers. Passed decent hex values (0x100, etc), it again doesn't say anything, even error (proper fix is to support hex numbers here, but error checking/reporting should happen everywhere).
@nekromant
Copy link
Owner

I know. So far I'm just playing with their weird API making sense of the minefield ahead. This is to be expected, it's not even alpha. The commands are just the underlying API exposed to experiments mostly.

iwconnect starts the connection process. always. No reboot is necessary.
iwmode applies immediatly. no reboots necessary.
spi_dump is currently a quick hack for debugging.

I'm now trying to get things work with proper newlib instead of a blob, and will be pushing a set of changes sometime next week. For now I want to set default .text location to irom0.text, instead of RAM, IROM_FLASH_ATTR is very ugly and make some changes to microrl itself.

Those are annoying and you're free to fix those, while I'm playing with the rest stuff - feel free to submit pull requests. I'll push some trivial fixes today that allow to use stuff like scanf from newlib - that should make things easier.

@pfalcon
Copy link
Contributor Author

pfalcon commented Nov 19, 2014

Ok, to continue the topic, that new "poke" thing is confusing too. Last thing I would think that it sends data to a remote host. Can we please have it named just "send"?

@nekromant
Copy link
Owner

Done.

@pfalcon
Copy link
Contributor Author

pfalcon commented Nov 19, 2014

Thanks!

@kozy
Copy link

kozy commented Nov 24, 2014

Enlightening. Thanks!

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

No branches or pull requests

3 participants