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

Upgrade to Tock-1.5-rc2 #97

Merged
merged 2 commits into from
Apr 24, 2020
Merged

Upgrade to Tock-1.5-rc2 #97

merged 2 commits into from
Apr 24, 2020

Conversation

gendx
Copy link
Collaborator

@gendx gendx commented Apr 24, 2020

Tock is making a 1.5 release: tock/tock#1685. Let's upgrade to that.

The last upgrade of Tock was made a couple weeks ago, so apart from minor changes in tock/tock#1648 and tock/tock#1750, OpenSK shouldn't be affected.

  • Tests pass
  • Appropriate changes to README are included in PR

@gendx
Copy link
Collaborator Author

gendx commented Apr 24, 2020

Tested on nRF52840-DK on (Chrome browser):

with the following configurations:

  • ./deploy.py --board nrf52840dk --opensk
  • ./deploy.py --board nrf52840dk --crypto_bench
  • ./deploy.py --board nrf52840dk --opensk --panic-console. For this configuration, also tried the "cancel touch" flow on Chrome.
  • ./deploy.py --board nrf52840dk --opensk --panic-console --verbose. Compiles and flashes properly, but still fails due to The --verbose mode is impractical #89.
  • ./deploy.py --board nrf52840dk --opensk --panic-console --debug. Sometimes hit the console "freeze" likely caused by [Bug] Incorrect VirtualMuxAlarm implementation tock/tock#1651.

@gendx gendx merged commit dc12e10 into google:master Apr 24, 2020
@gendx gendx deleted the tock-1.5 branch April 24, 2020 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants