wisp / wisp5 Goto Github PK

The WISP does not correctly interpret or respond to a BlockWrite command. The BlockWrite command is important because it allows multi-word writes and therefore higher throughput data transfer to the WISP.

In WISP_dataStructInterface_t, the readBufPtr and blockWriteBufPtr is an uint8_t instead of the suggested/intended uint16_t.

http://wisp5.wikispaces.com/WISP+Hardware is now 404, plz check

Add UART RX functionality to wisp-base.

See TODO: https://github.com/wisp/wisp5/blob/640kHz/CCS/wisp-base/wired/uart.c#L125

The WISP is setup and running on 8 MHz because of wisp_init.c
CSCTL1 = DCORSEL + DCOFSEL_3; //8MHz

The receiving part of the RFID stack is also supposed to run on 8 MHz, but in reality it runs on 16 MHz.
MOV.W #(DCORSEL|DCOFSEL_4), &CSCTL1

This causes a LOT of mistimings if everything was actually programmed assuming it was for a 8 MHz clock. It would also explain the reason why delimiters (and maybe other things) were way off since 1 clock cycle at 8 MHz = 0.125 us and 1 clock cycle at 16 MHz = 0.0625 us.

The two communication modes (uplink LF=640kHz and uplink LF=160kHz) represented by the '640kHz' branch and 'master' branch, respectively, need to be consolidated. It is increasingly unwieldy to keep them alive in separate branches, and therefore both users and developers could benefit from consolidation.

I propose that we have the WISP automatically choose a mode based on the reader's requested protocol spec in the Query command. This shouldn't be a tremendously difficult task. For simple clock adjust routines, use of function pointers may help simplify the implementation of a multiprotocol WISP. Most everything else falls into place with a simple clock adjustment for switching btwn these two protocols.