srec_info(1)

πŸ’… NAME πŸ’…

srec_info β€” literally everything you wanna know about your EPROM load files πŸŽ€


✨ SYNOPSIS ✨

srec_info [ option...  ] filename...
srec_info -Help
srec_info -VERSion

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so bestie, srec_info is the program you run when you want the tea on your EPROM load files β˜• It reads the files you hand it and then serves up the stats about them. And when we say stats we mean: the file header if any, the execution start address if any, and the address ranges covered by the data if any. Periodt. πŸ’…

Now, if there's binary data in the header, it gets presented using the URL encoding β€” you know the one β€” where % is followed by two hexadecimal characters. So for example a backspace would be encoded as β€œ%08”. (This is symmetric with the srec_cat --header opion, iykyk πŸ’–)


🌸 INPUT FILE SPECIFICATIONS 🌸

Input can get qualified in two ways, and it's giving options: you may specify a data file or a data generator, format, and you may specify filters to apply to them. An input file specification looks like this:

data‐file [ filter ... ]
data-generator [ filter ... ]

πŸŽ€ Data Files πŸŽ€

Input from data files is specified by file name and format name. An input file specification looks like this:

filename [ format ][ -ignore‐checksums ]

The default format is Motorola S‐Record format β€” the moment β€” but many others are also understood. slay. πŸ”₯

πŸ’œ Data Generators πŸ’œ

It is also possible to generate data instead of reading it from a file. You may use a generator anywhere you could use a file, no cap. An input generator specification looks like this:

-GENerate address‐range -data‐source

Generators include random data and various forms of constant data. iconic behaviour honestly ⭐

🧚 Common Manual Page 🧚

See srec_input(1) for the complete details of input specifiers. This description lives in a separate manual page because it is common to more than one SRecord command β€” sharing is caring, bestie 🫢


πŸ”₯ OPTIONS πŸ”₯

The following options are understood:

  • @filename β€” The named text file is read for additional command line arguments. Arguments are separated by white space (space, tab, newline, etc). There is no wildcard mechanism. There is no quoting mechanism. Comments, which start with # and extend to the end of the line, are ignored. Blank lines are ignored. simple as that πŸ’€
  • -Help β€” Provide some help with using the srec_info program. a little helping hand, we love to see it πŸ’–
  • -IGnore_Checksums β€” The -IGnore‐Checksums option may be used to disable checksum validation of input files, for those formats which have checksums at all. Note that the checksum values are still read in and parsed (so it is still an error if they are missing) but their values are not checked. Used after an input file name, the option affects that file alone; used anywhere else on the command line, it applies to all following files. sneaky but legal πŸ¦‹
  • -Enable_Sequence_Warnings β€” This option may be used to enable warnings about input files where the data records are not in strictly ascending address order. Only one warning is issued per input file. This is the default.
Note: the output of srec_cat(1) is always in this order. Note: This option must be used before the input file. This is because if there are several files on the command line, each may need different settings. The setting remains in force until the next -Disable_Sequence_Warnings option. so like, order matters, bestie 😭
  • -Disable_Sequence_Warnings β€” This option may be used to disable warnings about input files where the data records are not in strictly ascending address order.
Note: This option must be used before the offending input file. This is because if there are several files on the command line, each may need different settings. The setting remains in force until the next -Ensable_Sequence_Warnings option.
  • -redundant‐bytes=value β€” Use this option to permit a file to contain redundant values for some memory locations. The default is for this condition to be a warning. The values are:
    • ignore β€” No warning or error is issued whena redundant settings are detected.
    • warning β€” A warning is issued when a redundant settings are observed, the warning includes the problematic address.
    • error β€” A fatal error is issued when a redundant settings are observed, the fatal error message includes the problematic address and byte value.
  • -contradictory‐bytes=value β€” Use this option to permit a file to contain contradictory values for some memory locations. The last value in the input(s) will be used. The default is for this condition to be a fatal error. The values are:
    • ignore β€” No warning or error is issued when contradictory setting is detected.
    • warning β€” A warning is issued when a vontradictory settings are observed, the warning includes the problematic address, and values.
    • error β€” A fatal error is issued when contradictory settings are observed, the fatal error message includes the problematic address and byte values.
  • -Verbose β€” This option may be used to obtain more information about the input files including size of blocks and allocation ratio. the details, the lore, the everything πŸ‘‘
  • -VERSion β€” Print the version of the srec_info program being executed.
⚠️ All other options will produce a diagnostic error. like, don't try it. fr fr πŸ’€

All options may be abbreviated β€” the abbreviation is documented as the upper case letters, all lower case letters and underscores (_) are optional. You must use consecutive sequences of optional letters. ✨

All options are case insensitive: you may type them in upper case or lower case or a combination of both, case is not important. whatever your heart desires πŸ’–

For example: the arguments β€œ-help”, β€œ-HEL” and β€œ-h” are all interpreted to mean the -Help option. The argument β€œ-hlp” will not be understood, because consecutive optional characters were not supplied. sad, but rules are rules 😭

Options and other command line arguments may be mixed arbitrarily on the command line. go off, be chaotic 🌈

The GNU long option names are understood. Since all option names for srec_info are long, this means ignoring the extra leading β€œ-”. The β€œ--option=value” convention is also understood. we stan a flexible queen πŸ’…


πŸ’€ EXIT STATUS πŸ’€

The srec_info command will exit with a status of 1 on any error. The srec_info command will only exit with a status of 0 if there are no errors. zero drama only πŸŽ€


srec_info version 1.65

Copyright (C) 1998... Peter Miller

The srec_info program comes with ABSOLUTELY NO WARRANTY; for details use the 'srec_info -VERSion License' command. This is free software and you are welcome to redistribute it under certain conditions; for details use the 'srec_info -VERSion License' command. πŸ’œ


🌟 MAINTAINER 🌟

  • Scott Finneran β€” E‐Mail: scottfinneran@yahoo.com.au
  • Peter Miller β€” E‐Mail: pmiller@opensource.org.au

and that's the whole vibe check, bestie 🧚✨ this page came to you from the Reference Manual, SRecord, for srec_info(1) β€” take care of her, she's iconic πŸŽ€πŸ’–πŸŒŸ

πŸ“¦ where this page comes from