This reverts commit be820c07.

See merge request card10/firmware!343

See merge request card10/firmware!344

See merge request card10/firmware!342

Add a --set-time flag to allow setting card10 system time via the
USB-Serial connection.  Use like this:

    ./tools/pycard10.py --set-time

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!338

See merge request card10/firmware!335

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!334

See merge request card10/firmware!327

See merge request card10/firmware!326

Unify unrecoverable errors to use panic() in all cases.  This will allow
further changes to panic() to work for all critical errors.

Signed-off-by: Rahix <rahix@rahix.de>

Newlib assert uses __assert_func and thus our panic() function while
MXC_ASSERT uses a custom assertion logic.  Newlib assert is also more
portable as it works in expression position while MXC_ASSERT only works
as a statement.

Signed-off-by: Rahix <rahix@rahix.de>

Define `__assert_func()` so a failing `assert()` will trigger a panic.

Signed-off-by: Rahix <rahix@rahix.de>

In unrecoverable situations we should provide a common way to output the
cause of the error and then reset the CPU.  The panic() function is
mean to be exactly that.  It outputs the error-cause, stack-trace, and
firmware revision, accompanied by a link to the issue-tracker to
encourage people to report the error.  After a timeout of ~1.5s it
resets the CPU and reboots.

Future Work:

 - Right now, the stack-trace only has a depth of one which is the
   return address from where panic() was called.  In the future it might
   make sense to provide a deeper stack-trace if a robust implementation
   is possible.
 - Integration of @msgctl's faultscreen (!79) so users who don't have
   the serial console open at all times can also see what happened.

Signed-off-by: Rahix <rahix@rahix.de>

In severe error conditions, asynchronous prints will never work.  For
such cases we need a way to make prints happen synchronously again, the
same way it works during early boot.  Add a serial_return_to_synchronous()
function which unconditionally switches the serial driver code to
synchronous mode.

Only use this function in unrecoverable error conditions!

Signed-off-by: Rahix <rahix@rahix.de>

card10_reset() won't ever return to where it was called from.  Telling
the compiler this can help with program-flow analysis.

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!332

Philip Stewart authored 5 years ago and rahix committed 5 years ago

Fix two bugs in the display/gfx module:

1. The animation of the simple_menu used in the main menu had the issue
   that there is a black line visible at the top.  This is due the
   gfx_puts method ignoring lines, where the top pixel of the string is
   above the top of the screen.  As gfx_puts uses gfx_setpixel which in
   turn ignores pixels outside of the screen, remove the check in
   gfx_puts.
2. X and Y coordinates were cast to unsigned-ints before being given to
   the gfx-library which means calls like circ(0, -10, 30) would be draw
   at coordinates like [0,65526].  Fix this by changing the data-type of
   all coordinates to signed-integers.

Also remove the x and y ranges from the documentation of the individual
python functions and instead add a general documentation about the
screen and it's size/coordinate system.

fix(build): Fix module changes not getting picked up

See merge request card10/firmware!328

See merge request card10/firmware!294

Serge Bazanski authored 5 years ago and dx committed 5 years ago

We update the documentaiton and CI tooling to remove references to the jailbreak firmware.

We also slightly update the docs to mention USB mode in a separate page, for unification purposes.

See merge request card10/firmware!329

And show the no_apps_message instead of crashing

Previously, we left out the dependency of the QSTR header on
`modules.h`.  This was done to prevent rebuilds of the entire
MicroPython sources whenever a Pycardium module is changed. This
leads to issues where QSTRs got out of sync and weird errors like
the following could happen:

    import foo_module

    Exception: No module `abc_def` (a different string than expected)

Attempt to fix this by only updating the QSTR header when the
module-header actually changes.  For this, a few workarounds are needed:

- Replace symlinks with actual copied files so timestamps change on
  updates.
- Add a hack so meson picks up on the dependency of the file in genhdr/
- Rename the outer file so older meson versions don't complain about
  multiple targets with the same name.

Co-authored-by: dx <dequis@dequis.org>
Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!289

pycardium/utime: add unix_time and unix_time_ms

See merge request card10/firmware!290

Update BLE bianry blob, patch it and turn off encryption when needed

See merge request card10/firmware!319

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!103

Mateusz Zalega authored 5 years ago and rahix committed 5 years ago

Signed-off-by: Mateusz Zalega <mateusz@appliedsourcery.com>

Closes #171

See merge request card10/firmware!323

When MXC_ASSERT is disabled, the portexpander_config() call is not
compiled into the bootloader which leads to the portexpander not being
setup correctly and thus neither the screen turns on nor does the button
to switch into MSC mode work correctly (bootloader always goes into MSC
mode).

Fix this by moving the portexpander_config() call outside the MXC_ASSERT
and only keep the return value check inside.  Additionally fix the
pull-up/pull-down selection in portexpander_config() not being set
correctly.

Ref #171

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!320