A quick change in debugging documentation

[halazouna]

Box config called twice and we don't set up the heap_size :
debugging.md

/* Configure the debug box. */
UVISOR_BOX_NAMESPACE(NULL);
UVISOR_BOX_CONFIG(box_debug, UVISOR_BOX_STACK_SIZE); // box config called twice, and the heap size is not set up
UVISOR_BOX_MAIN(box_debug_main, osPriorityNormal, UVISOR_BOX_STACK_SIZE);
UVISOR_BOX_CONFIG(box_debug, acl, UVISOR_BOX_STACK_SIZE, box_context);

I have also some questions about the debug_box:
Does the system reboot only in release mode and not in the debug one? If so, can I reboot it after halting the system in debug mode?

Could we change the behavior of the system after catching an exception, like for example restarting just the box leading to the conflict?

Best regards,

[adbridge]

ARM Internal Ref: IOTSEC-247

[AlessandroA]

Hi @asensaoui thanks for reporting. #400 should fix the bug in the docs. As for your questions:

Does the system reboot only in release mode and not in the debug one? If so, can I reboot it after halting the system in debug mode?

Since uVisor 0.26.0 the debug box does not reboot automatically anymore. Upon return from the halt_error handler, the system halts.

You can still reboot the system if you want, by calling the NVIC_SystemReset() API. This is only possible from the debug box. It works both in debug and release mode:

static void halt_error(int reason) {
    printf("We halted with reason %i\r\n", reason);

    /* If we don't do anything, the system will halt upon return. */
    /* A debug box handler like this one can also decide to reboot the whole
     * system. This is only allowed from the debug box. */
    NVIC_SystemReset();
}

Could we change the behavior of the system after catching an exception, like for example restarting just the box leading to the conflict?

We do not support the reboot of a single box yet, but it's definitely something we would like to look into in the future.

[AlessandroA]

Fixed in #400.