Skip to content

Commit

Permalink
typos
Browse files Browse the repository at this point in the history
  • Loading branch information
doegox committed Apr 15, 2021
1 parent dda7ddb commit e62dfa3
Show file tree
Hide file tree
Showing 4 changed files with 12 additions and 12 deletions.
2 changes: 1 addition & 1 deletion armsrc/BigBuf.c
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,7 @@ uint32_t BigBuf_get_traceLen(void) {
/**
This is a function to store traces. All protocols can use this generic tracer-function.
The traces produced by calling this function can be fetched on the client-side
by 'hf list raw', alternatively 'hf list <proto>' for protocol-specific
by 'hf list -t raw', alternatively 'hf list -t <proto>' for protocol-specific
annotation of commands/responses.
**/
bool RAMFUNC LogTrace(const uint8_t *btBytes, uint16_t iLen, uint32_t timestamp_start, uint32_t timestamp_end, uint8_t *parity, bool readerToTag) {
Expand Down
2 changes: 1 addition & 1 deletion client/lualibs/read15.lua
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ local function read15693(slow, dont_readresponse)
We start by trying this command:
MANDATORY (present in ALL iso15693 tags) command (the example below is sent to a tag different from the above one):
pm3> hf 15 info u
pm3> hf 15 info --ua
UID=E007C1A257394244
Tag Info: Texas Instrument; Tag-it HF-I Standard; 8x32bit
pm3>
Expand Down
12 changes: 6 additions & 6 deletions doc/new_frame_format.md
Original file line number Diff line number Diff line change
Expand Up @@ -288,10 +288,10 @@ USART_BAUD_RATE defined there
Receiving from USART need more than 30ms as we used on USB
else we get errors about partial packet reception

FTDI 9600 hw status ⇒ we need 20ms
FTDI 115200 hw status ⇒ we need 50ms
FTDI 460800 hw status ⇒ we need 30ms
BT 115200 hf mf fchk 1 dic ⇒ we need 140ms
FTDI 9600 hw status ⇒ we need 20ms
FTDI 115200 hw status ⇒ we need 50ms
FTDI 460800 hw status ⇒ we need 30ms
BT 115200 hf mf fchk --1k -f file.dic ⇒ we need 140ms

# define UART_FPC_CLIENT_RX_TIMEOUT_MS 170
# define UART_USB_CLIENT_RX_TIMEOUT_MS 20
Expand All @@ -307,7 +307,7 @@ it's reduced to UART_USB_CLIENT_RX_TIMEOUT_MS.

Add automatically some communication delay in the `WaitForResponseTimeout` & `dl_it` timeouts.
Only when using FPC, timeout = 2* empirically measured delay (FTDI cable).
Empirically measured delay (FTDI cable) with "hw ping 512" :
Empirically measured delay (FTDI cable) with "hw ping -l 512" :

usb ⇒ 6.. 32ms
460800 ⇒ 40.. 70ms
Expand Down Expand Up @@ -453,7 +453,7 @@ On linux UART (FTDI)
CMD_PING reply_ng(CMD_PING, PM3_SUCCESS, packet->data.asBytes, packet->length);
<-12=504d33620080000009016233 <- NG

`hw ping 512` (NG)
`hw ping -l 512` (NG)

CmdPing SendCommandNG(CMD_PING, data, len);
->522=504d336100820901000102030405060708090a0b0c0d0e0f1011121314151617 -> NG
Expand Down
8 changes: 4 additions & 4 deletions include/pm3_cmd.h
Original file line number Diff line number Diff line change
Expand Up @@ -860,10 +860,10 @@ typedef struct {

// Receiving from USART need more than 30ms as we used on USB
// else we get errors about partial packet reception
// FTDI 9600 hw status -> we need 20ms
// FTDI 115200 hw status -> we need 50ms
// FTDI 460800 hw status -> we need 30ms
// BT 115200 hf mf fchk 1 dic -> we need 140ms
// FTDI 9600 hw status -> we need 20ms
// FTDI 115200 hw status -> we need 50ms
// FTDI 460800 hw status -> we need 30ms
// BT 115200 hf mf fchk --1k -f file.dic -> we need 140ms
// all zero's configure: no timeout for read/write used.
// took settings from libnfc/buses/uart.c

Expand Down

0 comments on commit e62dfa3

Please sign in to comment.