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

Cat-Dev's with older MION FW fail to boot even without PCFS #18

Open
Mythra opened this issue Nov 17, 2024 · 2 comments
Open

Cat-Dev's with older MION FW fail to boot even without PCFS #18

Mythra opened this issue Nov 17, 2024 · 2 comments

Comments

@Mythra
Copy link
Contributor

Mythra commented Nov 17, 2024

got another cat-dev today who's MION was running v0.0.14.70 compared ot the one I, gerbilsoft, and (I believe?) crediar have been testing with. This older MION FW does not implement the get_info action, or the power_on_v2 action. In fact it only implements two simple actions:

Unparsable line from body on mion/control.cgi: operation must be one of <power_on|set_param> operation_name=get_info

The older power_on also doesn't accept the emulation override that power_on_v2 does. This means I had to manually go in, and negate the signal going to "Disc-In" (otherwise it would claim there was no disc), and then manually send it a power on request.

For those who find this issue, and have a boot failure before I can fix it, the way to send a power on is with the following curl command:

curl -XPOST \
  -H "authorization: Basic bWlvbjovTXVsdGlfSS9PX05ldHdvcmsv" \
  -H "content-type: application/x-www-form-urlencoded" \
  --data-urlencode "operation=power_on" "http://$MION_IP/mion/control.cgi"

You may also want to go into the http://$MION_IP/http_pow_on_web.cgi url and hit "NEGATE" on Disc IN (you can also hit that power on button rather than through the curl command if you'd like).

@Mythra
Copy link
Contributor Author

Mythra commented Nov 26, 2024

I've got this working locally now on my branch implementing PCFS support:

terminal window printing out that a MION board was detected with old firmware, and powering on successfully.

However, I've also noticed a couple pretty egregious faults with the bridge targeting on selecting a CLI argument, and the setup page has been "default"'ing all this time without me noticing because I typo'd the setup route in the source code.... WHOOPS. This isn't too surprising given how much of a rush I was in to implement boot due to real life things.

Good news is that now I'm in no rush, and have holiday time, I've been able to perform quite a bit of cleanup. Not to mention thanks to crediar, I've got my hands on multiple new MION FW's, so this should be more resilient than ever.

@Mythra
Copy link
Contributor Author

Mythra commented Nov 26, 2024

If you're looking for the complete series of commands to run, to turn off the disc, and then power on the MION, the two requests you're ultimately looking at are:

# Eject any disc that may be in there at boot.
$ curl -XPOST \
  -H "authorization: Basic bWlvbjovTXVsdGlfSS9PX05ldHdvcmsv" \
  -H "content-type: application/x-www-url-formencoded" \
  "http://$MION_IP/mion/status.cgi" \
  -d 'operation=eject&disc=out&frommenu=no'
# Now send the boot command
$ curl -XPOST \
  -H "authorization: Basic bWlvbjovTXVsdGlfSS9PX05ldHdvcmsv" \
  -H "content-type: application/x-www-form-urlencoded" \
  --data-urlencode "operation=power_on" "http://$MION_IP/mion/control.cgi"

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

1 participant