_ _
__ ___ __ ___ ___ __ _ ___ | |_ ___ ___ | |___
\ \/ / '_ ` _ \/ __|/ _` / __|_____| __/ _ \ / _ \| / __|
> <| | | | | \__ \ (_| \__ \_____| || (_) | (_) | \__ \
/_/\_\_| |_| |_|___/\__, |___/ \__\___/ \___/|_|___/
|___/
Little python helpers for parsing through Xilinx build outputs.
### WORK IN PROGRESS
There are some blatant problems:
- unhandled exceptions on some message types
- duplicated messages reported
- etc
### Install
This is pure python, no dependancies. Only tested on linux (debian wheezy).
Using pypi:
pip install xmsgs-tools
Or, locally,
python setup.py install
### Usage
Do ``xmsgsprint -h`` or ``xmsgsdiff -h`` for usage. Examples:
bnewbold@ent$ xmsgsprint test/run_a/xst.xmsgs -t severe -f
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 2-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 4-bit target.
HDLCompiler:413: Result of 9-bit expression is truncated to fit in 8-bit target.
HDLCompiler:413: Result of 9-bit expression is truncated to fit in 8-bit target.
HDLCompiler:413: Result of 9-bit expression is truncated to fit in 8-bit target.
HDLCompiler:413: Result of 3-bit expression is truncated to fit in 2-bit target.
HDLCompiler:413: Result of 9-bit expression is truncated to fit in 8-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 2-bit target.
HDLCompiler:413: Result of 3-bit expression is truncated to fit in 2-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 9-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 12-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 4-bit target.
HDLCompiler:413: Result of 32-bit expression is truncated to fit in 5-bit target.
=== Summary ==================================================================
Severe Warnings: 13
bnewbold@ent$ xmsgsdiff test/run_a test/run_b --by-file -i 2261 2677 37 647 -s "*main*" -t warning
--- <unknown>
+Xst:0: Value "<PROCESSOR name={system} numA9Cores={2} clockFreq={666.66666...
+Xst:2254: Area constraint could not be met for block <main>, final ratio i...
=== Summary ==================================================================
Warnings: 153 (+2, -0)
### Example Raw .xmsgs
<msg type="warning" file="Xst" num="37" delta="new" >Detected unknown constraint/property "<arg fmt="%s" index="1">x_interface_info</arg>". This constraint/property is not supported by the current software release and will be ignored.
</msg>
<msg type="info" file="Xst" num="3210" delta="new" >"<arg fmt="%s" index="1">/home/bnewbold/leaf/twl/dds/hdl/block_design/ip/block_design_axi_gpio_0_0/synth/block_design_axi_gpio_0_0.vhd</arg>" line <arg fmt="%s" index="2">167</arg>: Output port <<arg fmt="%s" index="3">gpio_io_o</arg>> of the instance <<arg fmt="%s" index="4">U0</arg>> is unconnected or connected to loadless signal.
</msg>
### Notes
'fulltext' is not a unique identifier; many warning texts are repeated
See also, XReport GUI tool.
### TODO
- Are message numbers unique across tools? If not, need more sophisticated filtering.
- Collapse redundant warnings (eg, every bit on on the same port)
Metadata
Release files for xmsgs-tools 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xmsgs-tools-0.2.1.tar.gz | 5.6 kB | Without provenance | Details for xmsgs-tools-0.2.1.tar.gz |
Release files / xmsgs-tools-0.2.1.tar.gz
| Download URL | xmsgs-tools-0.2.1.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4108284459cf07e2d20c39ac4300a3f98e365c8504b18380366218f9c62fd5c3
|
|
BLAKE2b-256 checksum How to use checksums |
80675cae277601dda8f865550300b6ee258d6bcb7cc5efc7c722dd8cd892b06c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for xmsgs-tools 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.