openpcd/firmware, branch master Firmware for the OpenPCD, OpenPICC and SIMtrace hardware https://git.gnumonks.org/cgit/openpcd/atom?h=master 2015-09-28T15:02:22+00:00 convert from u_int*_t to uint*_t 2015-09-28T15:02:22+00:00 Harald Welte laforge@gnumonks.org 2015-09-28T15:00:51+00:00 urn:sha1:21391e0bdbe676ab766204eaa0eddd46e529c849 improve handling of spurious IRQs 2014-11-11T21:30:55+00:00 Min Xu min.xu@min-info.net 2014-10-25T20:08:04+00:00 urn:sha1:b6caca4b64a73d8d3ab4ce6b51cea71b8f1a54b0 rather than printing directly from the interrupt handler, just increment the number and print it from the main loop function instead. Allow some USB interrupts to be handled during dbgu_append 2014-11-11T21:30:55+00:00 Min Xu min.xu@min-info.net 2014-10-25T20:04:30+00:00 urn:sha1:478c2332b74c3ee7dfd8d70873419cf0ef19619e Retrieve + print previous PC from stack to debug wdog/spurious IRQ 2014-11-11T21:30:55+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:30:23+00:00 urn:sha1:8701086cacca088ae34580908cec45f77042b94e Retrive previous PC from the stack before entering specific interrupt handler routines. Allow user to trace where interrupt occured: e.g. WatchDog and Spurious interrupt Prior to this change, spurious interrupt would occur so much (observed via gdb/remote debug) so it appears that the board stalled. Once a custom spurious interrupt installed, the code continues after the interrupt instead of re-entering the interrupt. Don't split req_ctx with ATR payload 2014-11-11T21:30:55+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:25:54+00:00 urn:sha1:6bafd0cfb40c2d201f8723a3678dd4f04b380842 The codnition for flushing a req_ctx on UART idle is fixed to flush only if 1) There has been no new data since last check, and 2) There are no req_ctx currently pending to be transmitted to USB, and 3) We did NOT just got a reset and waiting for ATR I saw an ATR split in two different req_ctx prior, presumably flush decided to send req_ctx after ATR but got a new character just before sent). If we did get a RESET, let original logic decide to send the req_ctx -- presumably when ATR data is fully received. iso_uart: Print more errors, not just overruns 2014-11-11T21:30:54+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:18:03+00:00 urn:sha1:7e3c9959e1e140753738be9b6d4142f6c2068e3d change number + qty of small/large req_ctx 2014-11-11T21:30:54+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:09:19+00:00 urn:sha1:9662f2830a076a089373f3a4e6ecd93515cd108f pcd_enumerate: More complete USB endpoint resetting 2014-11-11T21:30:54+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:09:03+00:00 urn:sha1:4b98ba5d1c13aa620749997f85f24b20acf9ae69 req_ctx: Keep statistic about number of req_ctx in given state 2014-11-11T21:30:54+00:00 Min Xu min.xu@min-info.net 2014-10-25T19:05:37+00:00 urn:sha1:3cd467a8ef49a2f1d047c24a50832b5c82c405c8 ... and print this from a debug statement. Ensure to transmit current req_ctx on RESET/VCC events 2014-11-11T21:30:54+00:00 Min Xu min.xu@min-info.net 2014-10-25T18:55:01+00:00 urn:sha1:ab325fc295a23d04f27cc7300b12d2564e4d83e6 When any of the following events occur: * VCC_PHONE off * nRST * RST we tranmsit the current req_ctx, if there is data pending. This ensures that for any successive data, the ATR flag in the next req_ctx containing the data, not in the previous req_ctx. It also ensures that the ATR is aligned at 0 offset in the new req_ctx, which is an assumption the host software makes but the previous code didn't ensure. Furthermore, we introduce a periodic flushing of any pending but incomplete req_ctx.