Pixel to Byte
7208 - Pixel-to-Byte IP version 1.5: Why does the byte data from Pixel-to-Byte IP version 1.5 shows missing pixels data?
Description: There is a known issue in Byte to Pixel IP version 1.5, which it causes the MIPI data packets missing. Solution: There is no planned fix for version 1.5. Please upgrade the IP to version 1.6 or above.
6197 - All Nexus: Is Pixel to Byte IP's (P2B) RGB666 tightly packed?
RGB666 is only packed, thus, can only see data type 1E. The user can still use RGB666 loosely packed using RGB888 since the mapping are the same. For the loosely packed, it need to zero out input bits [7:6], [15:14] and [23:22]. In pixel-to-byte GUI, ...
5788 - [Pixel to Byte Converter IP Core]: How to control the input signals (fval_i/dval_i/txfr_en_i/txfr_req_o)?
The fv_i and lv_i signals are only for CSI-2 mode, and unused in DSI mode. The user can leave it undriven if they are using DSI mode. If, however, they are using it for CSI mode, these signals should indicate frame valid and line valid pulses. The ...
5642 - Crosslink : Can the Crosslink support ITU BT.1120?
Our CMOS to DPHY IP expects explicit syncs from the upstream device. From the BT.1120 spec, it looks like it send EAV & SAV code which has the embedded sync information. Our existing IP cannot support this. To support BT.1120, the customer would need ...