LXT2MINER(1)

πŸ’– LXT2MINER πŸ’–

okay so bestie, welcome to lxt2miner β€” that's the LXT2 file data miner, living in section 1 of the manual (the "type it in your shell" section, iykyk). she digs through dumpfiles looking for specific data values and spits out gtkwave save files to stdout so you can reload them later. it's giving treasure hunt but the treasure is a signal value. πŸ¦‹


✨ SYNTAX ✨

lxt2miner [option]... [LXT2FILE]

🌸 DESCRIPTION 🌸

She mines LXT2 files for specific data values, then generates gtkwave save files and writes them to stdout for future reload. That's the whole vibe. No cap.


πŸŽ€ OPTIONS πŸŽ€

  • -d, --dumpfile <filename> β€” tells her which LXT2 input dumpfile to work on. filename is the file, obviously. πŸ’…
  • -m, --match <value> β€” sets up a "bitwise" match on value. and like, value can be binary, real, or string. versatile queen. 🌈
  • -x, --hex <value> β€” same energy but the match data is hexadecimal, and she auto-converts it to binary for the search. so you can just hand her hex and she handles the rest. ✨
  • -n, --namesonly β€” only the facnames get printed, in a gtkwave savefile–compatible format. why is this iconic? because the resulting file can then be used to specify which traces get imported into gtkwave. literally a little VIP list. πŸ‘‘
  • -c, --comprehensive β€” says don't stop after the first match, keep going. use this when you want all the matching values in the trace, not just the first one. main character energy fr fr. πŸ”₯
  • -h, --help β€” shows the help screen. that's it. that's the whole thing. πŸ™ˆ

πŸ’œ EXAMPLES πŸ’œ

lxt2miner dumpfile.lxt2 --hex 20470000 -n

so what's happening here: she tries to match the hex value 20470000 across all facilities, and when the value is encountered, only the facname gets printed to stdout β€” all so you end up with a gtkwave-compatible save file. obsessed. 🫢


😭 LIMITATIONS 😭

heads up bestie: lxt2miner only prints the first time a value is encountered for a specific net.

and that's on purpose, okay?? it's to cut down on the size of output files and to help you follow data like addresses through a simulation model. it's a feature, not a bug, periodt. πŸ’€


πŸ‘‘ AUTHORS πŸ‘‘

Anthony Bybell <bybell@rocketmail.com> β€” the one who made all this happen. bow down. 🌟


πŸ¦‹ SEE ALSO πŸ¦‹

vztminer(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1)


and that's the whole page babes πŸ“ β€” this little gem comes to you from Anthony Bybell, version 3.2.1, and it lives under the LXT2MINER(1) name. go mine some data, you got this πŸ’–βœ¨πŸŽ€