How MIFARE Uses Cookies

[atramsz]

Hi,
The problem was with not adequate documents and type of protocol.
I bought CLEV663B Blueboard in version 3.0 – originally provided with SPI.
Example projects in LPCspresso are in I2C.
So either I change board on I2C or project configuration on SPI.
That is why I could properly connect with LPC board but blueboard did not reply.

Why this problem arose:
With this blueboard I received pdf files in which board schematics looked different from the board that I received but are marked as version 3.0. Actually it is 2.1 version. Someone just change the mark on the board not checking if it corresponds.
In AN11211 Rev 1.1 – 4 July 2013 226211 page 9.
“The Blueboard is generally delivered in I2C configuration for this reason one only needs to change the configuration if the use of the board in SPI configuration is desired.”
I assumed that version 3.0 will be also delivered with I2C. And here I was wrong. In this document there is no reference to version 3.0.
In chapter 2.7 you can of course change I2C to SPI but the bridge`s number R15,R11 etc are not the same in blueboard version 2.1 and 3.0.

So if you have:
- Blueboard version 2.1 – it is configured in I2C
- Blueboard version 3.0 – it is configured in SPI
- Example projects are for I2C.

Maybe there should be some function in example project testing whether the board works in the same protocol as the project?

---

+ 0  |  - 0

[atramsz]

I had to cope with it by myself but I made it. :D

---

+ 0  |  - 0

[atramsz]

Maybe I add that when I Debug the project USB Device with DFU Capabilities disappear from Control Settings/ Device manager.
I connect each board with USB port.

Hope someone will have an idea what to do. Laughing out loud

---

+ 0  |  - 0

[Author]

Posts