I discovered while working on the SAMV7 mcan driver that the implementation of the CAN error handling is suboptimal. In the current implementation the following errors are implemented as pending errors:

* Receiving
  * MCAN_INT_STE (Stuff Error)
    More than 5 equal bits in a sequence occurred.
  * MCAN_INT_CRCE (CRC Error)
    Received CRC did not match the calculated CRC.
  * MCAN_INT_RF0L (Receive FIFO 0 Message Lost)
    Receive FIFO 0 message lost, also set after write attempt to Receive FIFO 0 of size zero.
  * MCAN_INT_RF1L (Receive FIFO 1 Message Lost)
    Receive FIFO 1 message lost, also set after write attempt to Receive FIFO 1 of size zero.

* Sending
  * MCAN_INT_BE (Bit Error)
    Device wanted to send a rec / dom level, but monitored bus level was dominant / recessive.
  * MCAN_INT_TEFL (Tx Event FIFO Element Lost)
    Tx Event FIFO element lost, also set after write attempt to Tx Event FIFO of size zero.

* General
  * MCAN_INT_MRAF (Message RAM Access Failure)
    The flag is set, when the Rx Handler
    * has not completed acceptance filtering or storage of an accepted message until the arbitration field of the following message has been received. In this case acceptance filtering or message storage is aborted and the Rx Handler starts processing of the following message.
    * was not able to write a message to the Message RAM. In this case message storage is aborted. In both cases the FIFO put index is not updated resp. the New Data flag for a dedicated Receive Buffer is not set, a partly stored message is overwritten when the next message is stored to this location. The flag is also set when the Tx Handler was not able to read a message from the Message RAM in time. In this case message transmission is aborted. In case of a Tx Handler access failure the MCAN is switched into Restricted Operation mode (see Section 47.5.1.5). To leave Restricted Operation mode, the processor has to reset MCAN_CCCR.ASM.
  * MCAN_INT_ELO (Error Logging Overflow)
    Overflow of CAN Error Logging Counter occurred.

The listed errors are not pending, the errors occurred and are gone directly afterwards. This commit changes the described behavior and simplifies the handling of CAN errors.

I'm working on bringing up USB full-speed support on STM32F405.  My board does not include a USB power switch, VBus sensing, over current detection, or ID pin.

This commit add a config STM32_OTGFS_VBUS_ CONTROL which lets us selectively disable VBus sensing and control.  I also sneaked in a change to disable the configgpio call for the ID pin, which is only used in OTG mode which isn't supported yet.  The only pins that need to be initialized should be OTGFS_DP and OTGFS_DM.

These changes let a USB mouse enumerate on my platform if it's plugged in on power-up.  Plugging, unplugging, clicking, or moving the mouse cause NSH to stop responding.  Because I'm using the ramlog, I don't have useful debug messaging yet, so there's a lot more work I have to do to troubleshoot it or get my JTAG debugging set up, but these patches shouldn't hurt anything.  I'm hoping my issue is something simple I overlooked in configuration.

I'm planning to add similar changes for the OTGHS peripheral (using integrated full speed phy) but I still need to test those changes before submitting patches.

Spirit bugfixes:  Was hanging occasionally because there was not mechanism to restart the poll timer if poll was not performed because Spirit ws busy.  Fixed by not checking if Spirit is busy.  The TX poll can be performed asynchronouly while spirit is busy; any outgoing data will queued until Spirit is ready. Fixed handling of a timeout condition.  Failure to transmition to the TX state would fail (timeout) if in a race condition Spirit already committed to the RX state.  The driver needs to recover the state properly and avoid debug assertions in this event.

sched/: Fix return value in sched_setaffinity()

Approved-by: Gregory Nutt <gnutt@nuttx.org>

TX timeout must also be cancelled on a TX error.  TX timeout should check if we are waiting for a TXto complete.  TX timeout was too short (short than the maximum number of retries).

Spirit network driver:  TX timeout was never being cancelled!  Also reviewed and cleaned up all error handling logic

6LoWPAN:  When obtaining the radio MAC address from the IP address, handle the special case of broadcast and multicast address.

STM32F103-Minimum: (1) Enable CONFIG_MTD_PARTITION in Kconfig if flash partition is enabled and (2) Update the README.txt file with info needed to get SmartFS working.

Spirit:  Restore the 96 byte maximum packet length.  Reducing the packet length had no effect on eliminating RX FIFO errors.

Spirit Network Driver:  Add support for watermark interrupts on RX FIFO.  Reduce max packet length to avoid an errata.

IEEE 802.15.4 network drivr:  Fix more compile issues that only show up when CONFIG_NET_STARPOINT is defined.

IEEE 802.15.4 network driver:  Fix some errors introduced in previous commit.  Clean up some of the casting logic.

Spirit + 6LoWPAN:  In STAR configuration, Spirit must use a configured well known hub address.  6LoWPAN cannot assume that the PAN coordinator is the STAR hub; it must ask the radio to provide it with the address of the star hub

B-L475E-IOT01A: Make spirit-6lowpan configuration match what is currently under test:  Enable multicast, broadcast, but disable CRC support.  Currently CRCs are not working right.

Spirit: Increase number of retries if there is no acknowledgement; Add interrupt handling for the case where the max number of retries expires.  Fix some badly implemented queue management code.  With these changes the basic UDP and TCP tests work.

Spirit:  Convert network driver to use STack packets vs. Basic packets.  We need to use the STack packets in order to provide the source address.

Spirit: Correct setting of the length width field; Add multicast and broadcast addresses to radio properities.

Spirit network driver:  Need to enable sending of TX address.  Moved some non-optional settings out of board.h to driver.

RAMTRON:  Should be able to select chunked write mode via a configuration option, not by editing the file.

RAMTRON: Add support for splitting block writes in chunks.  Some Re-RAMs like MB85AS4MT has a write buffer size limitation.

drivers: handle I2C_TRANSFER return value consistently.  Some I2C peripherals transfers return zero on success, others number of completed transfers. Make drivers robust against this.