# Axilite\_check problem

**URL:** <https://forum.uvvm.org/t/axilite-check-problem/63>\
**Category:** Bitvis VIP AXI-Lite\
**Tags:** uvvm, axilite\
**Created:** [May 19, 2020, 10:46pm UTC](https://forum.uvvm.org/t/axilite-check-problem/63 "2020-05-19T22:46:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mergani](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mergani](https://forum.uvvm.org/u/mergani)\
**Post date:** [May 19, 2020, 10:46pm UTC](https://forum.uvvm.org/t/axilite-check-problem/63/1 "2020-05-19T22:46:38Z")

</div>

Hi everybody,  
When I tried to read data from registers on axilite, I see below message.  
Both expected and got mesaage same, but it failed.  
Do I miss something? I checked waveform interface, it seems no problem.  
bitvis\_vip\_axilite version 2.6.1

Thanks!

```
UVVM: 
UVVM: =========================================================================================================================================================================
UVVM: ***ERROR #1***
UVVM: 723857.5 ns AXILITE_VVC,1
UVVM: axilite_check(A:x"0", x"0000010C")=> Failed. slv Was x"0000010C". Expected x"0000010C".
UVVM: 'Check data from TMP112_MEAS from axi interface' [22]
UVVM: =========================================================================================================================================================================
UVVM: 
UVVM:
```

---

<div class="post-metadata">

**Author:** ![Erick](https://avatars.discourse-cdn.com/v4/letter/e/bbce88/32.png) [@Erick](https://forum.uvvm.org/u/Erick)\
**Post date:** [May 26, 2020, 1:48pm UTC](https://forum.uvvm.org/t/axilite-check-problem/63/2 "2020-05-26T13:48:14Z")

</div>

Hi,

This error is due to the comparison of ‘H’ and ‘1’ values inside the std\_logic\_vector.  
Since the comparison of ‘H’ and ‘1’ being true is dependent on each application this is not a UVVM problem, however we will add in the next release a configuration element in the BFM to select the match strictness desired so that the comparison can either be true or false. We will also improve the alert log to print a binary value in this case so that it is easier to know what the error is.

Best regards,  
Erick