Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rarely, HSB does not forward data recevied on the MIPI interface, resulting in an "Ingress frame timeout; ignoring." message. #5

Open
p-ogrady opened this issue Aug 26, 2024 · 0 comments

Comments

@p-ogrady
Copy link
Collaborator

An initialization bug in the FPGA MIPI receiver block IP sometimes causes data to be dropped before being delivered to the FPGA's UDP packetizer; resulting in no sensor data being delivered to the host. If you've commanded a camera to send image data, but no data is observed and the timeout message is displayed, you can verify that this is the cause by issuing these commands within the HSB demo container:

hololink read_uint32 0x50000000   # for the first camera
hololink read_uint32 0x60000000   # for the second camera

If a camera is configured to issue data, but a 0 appears in this memory location, then this is an indication that the receiver is in this stuck state. hololink.reset() is able to clear this condition. Work is underway with the IP vendor to resolve this condition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@p-ogrady and others