Closed andrewc-arm closed 3 years ago
I can reproduce this problem. It is just a warning. As pyOCD works with (=requires) older pyYAML, other package (earlier installed I believe) requests the newest version (I believe this could be progen as we do not have strict version there, I should fix that but that would be now >= 5.1, so this warning would be there anyway).
@flit Would it make sense to update pyOCD to use pyYAML >=5.1 ?
The latest pyocd (0.23.0 as of this writing) requires pyyaml >= 5.1. We just need to update the pyocd used in DAPLink.
Hi, @0xc0170 and @flit Then it seems we need to change this line to upgrade pyOCD? https://github.com/ARMmbed/DAPLink/blob/master/requirements.txt#L4
Correct, @andrewc-arm can you please send PR fixing it?
I think it's not quite that simple. The pyOCD API has probably changed some since 0.16.0 (can't remember details, but it's in the pyOCD release notes). I was going to attempt to get to it after the gcc port, but if someone else could take care of it that would be fantastic.
@andrewc-arm can you please send PR fixing it?
Sorry. I am new to DAPLink and even if took a hack at it, it would be dangerous. :) However, I will be mindful of tips and next time when I have to test DAPLink tests I will give it a try and share the opinion here.
I think it's not quite that simple. The pyOCD API has probably changed some since 0.16.0 (can't remember details, but it's in the pyOCD release notes). I was going to attempt to get to it after the gcc port, but if someone else could take care of it that would be fantastic.
I can have an attempt to at least get initial branch. I'll check it
@0xc0170 - any progress?
@0xc0170 - any progress?
Not yet, I was OoO most of the last weeks. I'll keep this open to check.
@flit: I guess since #746 was merged this should be closed.
Yep, thanks.
During the installation, I came across following ERROR. Is this OK?
The full log.