Project

General

Profile

Actions

Feature #5076

closed

Update board revision

Added by cibomahto about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

100%


Description

The board is currently marked as 'OpenVizsla v3.2', it should likely be increased.


Files

after.png View after.png 385 KB cibomahto, 04/06/2021 05:54 PM

Related issues

Related to OpenVizsla USB tracer/analyzer - Feature #5063: Allow un-powered operationResolvedcibomahto03/09/2021

Actions
Actions #1

Updated by mschramm about 3 years ago

  • Status changed from New to Feedback
  • Assignee set to laforge
  • Priority changed from Normal to Low
  • Start date deleted (03/15/2021)

I'm not convinced yet... those changes done (a few left) 'just' improve usability and mainly producibility. OTOH, changes like the filter network between USB shield and GND introduce new features, which could legitimate a next minor revision number.

laforge : what do you think? Maybe inquire @tmbinc about it too?

Actions #2

Updated by mschramm almost 3 years ago

Actions #3

Updated by mschramm almost 3 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Feedback to In Progress
  • Assignee changed from laforge to cibomahto
  • Priority changed from Low to Normal
  • % Done changed from 0 to 10

laforge decided to increase the minor by one, so let's make this a 3.3 in all places where version 3.2 is mentioned. Please then tag this with 'v3.3' when it gets merged upstream (Harald: @tmbinc might need to do this?)

If we one day implement #5063, I'd then vote for making these changes a v3.4 to have everything, which was solved until now as pr#43, a separate tag.

Actions #4

Updated by cibomahto almost 3 years ago

Implemented here: https://github.com/openvizsla/ov_ftdi/pull/46/commits/8289ce9d6d0fe8bfd663abc834f23487a805db31

I only see the version number referenced once, which is on the top silk of the PCB. Please let me know if you found any other occurrences.

Actions #5

Updated by cibomahto almost 3 years ago

Actions #6

Updated by cibomahto almost 3 years ago

Please then tag this with 'v3.3' when it gets merged upstream (Harald: @tmbinc might need to do this?)

I believe that is the case.

Actions #7

Updated by mschramm almost 3 years ago

  • Target version set to 3.3
  • % Done changed from 10 to 90

cibomahto wrote:

I only see the version number referenced once, which is on the top silk of the PCB. Please let me know if you found any other occurrences.

Only those ones the software seems to set automatically, e.g. for the dxf. But as you defined it globally(?), it appears in ov_ftdi.PrjPcb, so obviously the sw takes care for those references.

Solved, thanks!

I leave this open as a reminder for us resp. @tbminc regarding a git tag for it after upstream merge.

Actions #8

Updated by cibomahto almost 3 years ago

  • Assignee changed from cibomahto to mschramm
Actions #9

Updated by mschramm almost 3 years ago

while everything else has been made mainline, a request for adding those two tags (3.3 and 3.4) has not been followed (yet)... :\

Actions #10

Updated by laforge over 2 years ago

mschramm wrote:

while everything else has been made mainline, a request for adding those two tags (3.3 and 3.4) has not been followed (yet)... :\

just sent a reminder to tmbinc

Actions #11

Updated by mschramm over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

the two tags have been established:

  • d6f3ff5 became hardware_v3.3
  • 73ac5cb is hardware_v3.4
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)