Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors while compiling for Bus Pirate v3 and mismatched messages. #74

Closed
USBEprom opened this issue Nov 10, 2017 · 6 comments
Closed

Errors while compiling for Bus Pirate v3 and mismatched messages. #74

USBEprom opened this issue Nov 10, 2017 · 6 comments
Assignees
Labels
Milestone

Comments

@USBEprom
Copy link

I am sorry to keep annoy but while compiling for Bus Pirate v3 using the current November 07, 2017 repository still I have same problems as I wrote here:

#54 (comment)

Plus a dangerousprototypes' forum user noticed that some message into SPI protocol are wrong:

http://dangerousprototypes.com/forum/viewtopic.php?f=28&t=8498&p=67167#p67164

In detail the thing is that by performing some commands while in SPI mode then the Bus Pirate v3 use wrong messages on the terminal:

SPI>[0x9f r r r]
/CS ENABLED
WRITE: 0x9F
READ: 0xC2
READ: 0x20
READ: 0x14
\CS ENABLED
SPI>

It is only a cosmetic issue because actually, despite the wrong message, everything works as expected, but it is really annoying
For what I know the problem started with repositories dated after the April 10, 2017 because some custom firmware I build starting from that repository and I released on the dangerousprototypes' forum do not have it:

http://dangerousprototypes.com/forum/viewtopic.php?f=28&t=8498&p=67167#p67167

Thanks.

@agatti agatti self-assigned this Nov 12, 2017
@agatti agatti added the v3 label Nov 12, 2017
@agatti agatti added this to the 7.1 release milestone Nov 12, 2017
@agatti
Copy link

agatti commented Nov 12, 2017

@USBEprom I fixed the compilation error, but I wonder why it never triggered on my installation. Maybe from now on you may want to use a more modern version of MPLAB-X, v4.05 has been available for a week or two now.

@agatti
Copy link

agatti commented Nov 12, 2017

@USBEprom the backslash issue was fixed in 47f5c59 a couple of months ago, by the way.

I'm closing this since both issues seem to have been addressed, please reopen if those issues persist, thank you.

@agatti agatti closed this as completed Nov 12, 2017
@USBEprom
Copy link
Author

USBEprom commented Nov 12, 2017

@agatti

Thank you Sir, as usually you are the best!
Now it is possible to compile without errors but sadly still does not works because then there are not setting into menus' items as explained here:

#54 (comment)

However as you suggested me I am upgrading to MPLABX-v4.05 and xc16-v1.33 in order to exclude their fault.
Sadly my computer is running Windows XP and latest MPLABX-v4.05 does not work there.
I have to prepare a new environment.
I probably will use Linux.
I will send the result, thanks!

@USBEprom
Copy link
Author

USBEprom commented Nov 19, 2017

As promised today I was able to setup a Linux environment (Ubuntu LTS 16.04.3) where I installed MPLABX_v4.05 and xc16_v1.33 both fully working.
Using it I have built test firmwares starting from the current repository then sadly falling into the same problem described here:

#54 (comment)

The firmwares are compiled without error but the problem still arises and there are not setting into menus' items, almost them all are without options.
In the end it does not depend on obsolete MPLABX or XC16, the culprit has to be something else wrong that I have to believe is in the repository itself.

@USBEprom
Copy link
Author

A tiny news, if it can be useful.
Actually option items are not totally gone, in fact by using the command "W" [PSU (off/ON)] them all are there.
Seems to me that the warning

Clutch disengaged!!!
To finish setup, start up the power supplies with command 'W'

is triggered bad at the wrong time so then by sending the command "W" as suggested by the spurious message not only power supplies are switching ON but the missing options are shown on the terminal.
Here it is a simple example which explain the issue:

i
Bus Pirate v3.5
Community Firmware v7.1 - goo.gl/gCzQnW [HiZ 1-WIRE UART I2C SPI 2WIRE 3WIRE KEYB LCD PIC DIO] Bootloader v4.5
DEVID:0x0447 REVID:0x3046 (24FJ64GA00 2 B8)
http://dangerousprototypes.com
HiZ>m

  1. HiZ
  2. 1-WIRE
  3. UART
  4. I2C
  5. SPI
  6. 2WIRE
  7. 3WIRE
  8. KEYB
  9. LCD
  10. PIC
  11. DIO
    x. exit(without change)

(1)>5
Clutch disengaged!!!
To finish setup, start up the power supplies with command 'W'

Ready
SPI>W
POWER SUPPLIES ON
Set speed:

  1. 30KHz
  2. 125KHz
  3. 250KHz
  4. 1MHz
  5. 50KHz
  6. 1.3MHz
  7. 2MHz
  8. 2.6MHz
  9. 3.2MHz
  10. 4MHz
  11. 5.3MHz
  12. 8MHz

(1)>
Clock polarity:

  1. Idle low *default
  2. Idle high

(1)>
Output clock edge:

  1. Idle to active
  2. Active to idle *default

(2)>
Input sample phase:

  1. Middle *default
  2. End

(1)>
CS:

  1. CS
  2. /CS *default

(2)>
Select output type:

  1. Open drain (H=Hi-Z, L=GND)
  2. Normal (H=3.3V, L=GND)

(1)>
Clutch engaged!!!
SPI>w
Clutch disengaged!!!
POWER SUPPLIES OFF
SPI>W
POWER SUPPLIES ON
Set speed:

  1. 30KHz
  2. 125KHz
  3. 250KHz
  4. 1MHz
  5. 50KHz
  6. 1.3MHz
  7. 2MHz
  8. 2.6MHz
  9. 3.2MHz
  10. 4MHz
  11. 5.3MHz
  12. 8MHz

(1)>

I am going to open a new issue that match better the real behaviour of the thing, just in case.
Thanks.

@agatti
Copy link

agatti commented Nov 20, 2017

Ok, I'll close this one and move onto the other report, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants