Test transfer of messages smaller than 64 byte
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 19
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The smallest message size which can be configured in the example design is 64 bytes, which is the width of the FIFO. The aurora core itself sends messages in chunks of 32 bytes. This can be reached with setting the keep bits in a single transfer to half of the bytes. This should flush the datawidth converter and lead to a single transfer of the aurora core. With some small changes to the issue kernel, it could be verified, if this is really the case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the example design and its issue kernel, then trace how a single transfer uses keep bits and reaches the FIFO and Aurora core. Verify the behavior for a message smaller than 64 bytes; done means the kernel test confirms whether the datawidth converter flushes it into one Aurora-core transfer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100