FreeCalypso > hg > freecalypso-tools
view rvinterf/include/limits.h @ 505:7bf0d909c87e
fc-loadtool flash ID check: change of reset after the check logic
This change only affects those flash configurations that have ID checks
enabled. The logic for resetting the flash after the ID check has been
changed as follows:
1) If the check fails, we return without attempting to reset the flash.
2) If the check is successful, we reset the flash using the configured
method (could be AMD or Intel or Intel W30) instead of always doing an
AMD flash reset as the original code did.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Mon, 27 May 2019 19:58:01 +0000 |
parents | e7502631a0f9 |
children | ca6e969be6ee |
line wrap: on
line source
/* * For sizing our buffers etc in the rvinterf suite, including the local * UNIX domain socket protocol between rvinterf and fc-tmsh etc, we need * to have some limits on the message sizes in both host->target and * target->host directions. * * For the host->target direction, the choice of message size limit is * easy: the packet Rx code in RVT on the target side also has a limit * (quite naturally, as it needs to use a static buffer to reassemble * incoming packets as they arrive at the UART in unpredictable interrupt- * sized chunks), so we set our limit to match that in RVT. */ #define MAX_PKT_TO_TARGET 255 /* * In the other direction (target->host), there is no fixed limit * definition easily visible in the target fw code: any fw component * can call rvt_send_trace_cpy() or rvt_mem_alloc() followed by * rvt_send_trace_no_cpy(), or some higher-level API that reduces to * these functions, with a message of any size, subject only to memory * limits, which obviously aren't as strict as a #define'd maximum * message size. Hence in this direction we use our own arbitrary * choice of size limit. */ #define MAX_PKT_FROM_TARGET 512 /* * Both limit definitions above counts all bytes between the opening and * closing STX flags, but not DLEs inserted for binary transparency. */