Update esp-println requirement from 0.16 to 0.17 in /tests/xtensa

[dependabot]

Updates the requirements on esp-println to permit the latest version.

Release notes

Sourced from esp-println's releases.

0.17.0

Please note that only changes to the esp-hal package are tracked in these release notes. Read the full changelog entry for all the changes.

esp-hal@0.17.x Migration Guide

This release changes interrupt handler binding from link-time binding to runtime-binding. This increases flexibility of how interrupts can be used, but the main reason is two allow mixing mixing async and non-async drivers in the same application.

Key changes

The biggest change is the removal of the #[interrupt] macro. It has been replaced by the #[handler] macro which works differently slightly differently.

Now you have to bind the interrupt handler explicitly. The supported peripheral drivers either take a new optional parameter to their constructor or it will offer a set_interrupt_handler function. Don't worry, if you forget to do this, the compiler will emit an unused warning for the #[handler] function.

The second change is that most drivers will now have a MODE parameter with some new constructors to initialize a driver in Blocking or Async mode. You will need to account for this in your code.

Finally, most root level re-exports are now gone, instead, you should import from the specific module.

Below is a list of key changes you need to make to upgrade.

There is no longer a need to enable interrupts manually unless you are changing a priority later in the application. This change also means the interrupt is enabled once the interrupt is used, so please ensure that you have the proper ordering of initialization or critical sections to account for that.

- interrupt::enable(Interrupt::GPIO, Priority::Priority2).unwrap();

Use the new handler macro.

- #[interrupt]
+ #[handler]

Ensure you set the handler, depending on the peripheral this may be part of the constructor or a method such as the one below.

+ io.set_interrupt_handler(handler);

Interrupts are now tightly coupled to their priority, meaning you can pass a priority to the handler macro. The default unless specified is the lowest priority.

+ #[handler(priority = "Priority::max()")]

Commits

• 347003d update deps as cargo won't jump to 0.2.1 as 0.20 is yanked... sigh (#5386)
• 0cdb14b bump e-sync to 0.2.1, as we have a yanked 0.2 release (#5384)
• 2ce5ce1 Release 18 packages, including esp-hal@1.1.0-rc.0 (#5382)
• df7e89b add syslog qa test (#5381)
• 471703d make MSRV consistent (#5383)
• 689793b Process build-deps in relcheck (#5379)
• c8a2a60 misc improvements for the release tooling (#5377)
• 9c56205 Align ESP toolchain version (#5378)
• 1990c12 Don't offer CSI feature for C2 (#5370)
• 8b1995c Clean up tx_token (#5372)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)