--debug switch does not produce debugging messages

Bug #924422 reported by Christopher Wilson on 2012-01-31

This bug report was converted into a question: question #186439: Why doesn't "--debug" switch produce debugging messages?.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-msp430-tools
Undecided
zsquareplusc

Bug Description

The "--debug" switch doesn't appear to cause any change in the output (see below). Is it expected that there should be additional debug messages for this command?

Here's a transcript showing that "--debug" switch does not appear to produce any additional debugging messages:

$ msp430-bsl --swap-reset-test --invert-reset --invert-test --speed=38400 -r -e -p /dev/tty.usbserial-FCV6I5XN blink.hex
Programming: OK
$ msp430-bsl --swap-reset-test --invert-reset --invert-test --speed=38400 -r -e -p /dev/tty.usbserial-FCV6I5XN --debug blink.hex
Programming: OK
$ msp430-bsl --swap-reset-test --invert-reset --invert-test --speed=38400 -r -e -p /dev/tty.usbserial-FCV6I5XN -v blink.hex
Debug is False
Verbosity level set to 2
Python version: 2.7.1 (r271:86832, Jun 16 2011, 16:59:05)
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]
pySerial version: 2.6
action list:
   mass_erase()
   program_file()
   reset()
   reset()
Write segment at 0x4000 2490 bytes
Write segment at 0xffe0 32 bytes
Programming: OK
$ msp430-bsl --swap-reset-test --invert-reset --invert-test --speed=38400 -r -e -p /dev/tty.usbserial-FCV6I5XN -v --debug blink.hex
Debug is True
Verbosity level set to 2
Python version: 2.7.1 (r271:86832, Jun 16 2011, 16:59:05)
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]
pySerial version: 2.6
action list:
   mass_erase()
   program_file()
   reset()
   reset()
Write segment at 0x4000 2490 bytes
Write segment at 0xffe0 32 bytes
Programming: OK

Changed in python-msp430-tools:
assignee: nobody → zsquareplusc (zsquareplusc)
zsquareplusc (zsquareplusc) wrote :

--debug mainly changes how exceptions (internal errors) are displayed. For more detailed log messages of the programming progress, try -v (also multiple times like -vvv)

Christopher Wilson (cdwilson) wrote :

Ahh, i see. Ok, thanks. I'm converting this bug into a question (since it's not really a bug).

Changed in python-msp430-tools:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions