semvec/pypi-packages huggingface dataset:
tox-envreport 0.2.1
A tox-plugin to document the setup of used virtual environments.
License: MIT

=============
tox-envreport
=============

.. image:: https://img.shields.io/pypi/v/tox-envreport.svg
    :target: https://pypi.org/project/tox-envreport
    :alt: PyPI version

.. image:: https://img.shields.io/pypi/pyversions/tox-envreport.svg
    :target: https://pypi.org/project/tox-envreport
    :alt: Python versions

.. image:: https://travis-ci.org/useblocks/tox-envreport.svg?branch=master
    :target: https://travis-ci.org/useblocks/tox-envreport
    :alt: See Build Status on Travis CI

.. image:: https://ci.appveyor.com/api/projects/status/github/useblocks/tox-envreport?branch=master
    :target: https://ci.appveyor.com/project/useblocks/tox-envreport/branch/master
    :alt: See Build Status on AppVeyor

`tox-envreport` is a plugin for `tox <https://tox.readthedocs.io/en/latest/>`_
to document the setup of used virtual environments.

Collected information are stored in a file called ``env_report.json`` inside the `.tox` folder.
For example: ``MY_PROJECT/.tox/env_report.json``.

Installation
------------
``pip install tox-envreport``

Usage
-----

The installation of the plugin is enough to automatically activate it for each tox run.

There is nothing more to do or to configure.

Access reports
--------------
`tox-envreport` creates one common ``env_report.json`` file, which contains all information about all used virtual
environments (venv) by tox.

Beside this a venv specific file is generated as well and contains information about the related venv only.
You can find this file in the venv-specific tox-folder. E.g: ``MY_PROJECT/.tox/py27/env_report_py27.json``
for a venv called *py27*.

The report file itself contains the venv-name as postfix. E.g.: ``env_report_py27.json``.
imx-nand-tools 1.0.3
Freescale i.MX NAND reverse tools
License: MIT
Requires Python: >3.5.2
Keywords: imx freescale tool

i.MX NAND Tools for Freescale i.MX NAND Dumps
=============================================

Provides dedicated tools for IMX NAND dumps reverse-engineering:

* **imx-nand-info**: parse the FCB and display useful information about the Flash structure
* **imx-nand-convert**: parse the FCB and convert the actual dump into a memory-based image that can be processed with binwalk

How to install
==============

You can choose to either install *imx-nand-tools* from PyPi or from the source.

PyPi install
------------

That's the most easiest way to install *imx-nand-tools*:

::

        $ sudo pip3 install imx-nand-tools


It will install *imx-nand-tools* and all its dependencies. 


Install from source
-------------------

The following commands will install *imx-nand-tools* from source.

::

        $ git clone https://github.com/DigitalSecurity/imx-nand-tools.git
        $ sudo pip install setuptools
        $ cd imx-nand-tools
        $ python setup.py build
        $ sudo python setup.py install 

And that's it


How to use it
=============

imx-nand-info
-------------

This tool loooks for the first *Firmware Control Block* (FCB) contained in a dump and parse it and then
displays its contents.

::

        $ imx-nand-info fresh-dump.bin


imx-nand-convert
----------------

This tool converts a fresh i.MX NAND dump into a useable memory image:

::
  
        $ imx-nand-convert fresh-dump.bin converted-dump.bin


The *-c* option enables error correction thanks to embedded ECC information, thus *imx-nand-convert* will be able to fix potential errors in the original NAND dump.