-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
I made a ChameleonMini by your PCB design, and it works well, after I increased the UID, I want downlaod the changed dump file to find the differences between the file and origin file.
But after I se…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
```
What steps will reproduce the problem?
1. see additional info: C Source and Execution Results
2.
3.
What is the expected output? What do you see instead?
incorrect conversion of HEX literals
Wha…
-
Hi.
Peter, why do you use 130 bytes block?
> uart.on('data', 130, recv_block, 0)
As I see, it should be 132:
**soh, num, !num, data[128], crc**
You can read [Wiki](http://en.wikipedia.org/wiki/…
-
I am in the way of porting libhexabus to the go programming language, i just figured that
the crc might not be a standard 16 bit Kermit.
From what i reed the two crc bytes have to be swapped after ca…