Announcement
Collapse
No announcement yet.
User Profile
Collapse
-
I had a 15 5515 for repair this week, and looked at [URL="https://www.badcaps.net/forum/troubleshooting-hardware-devices-and-electronics-theory/troubleshooting-laptops-tablets-and-mobile-devices/schematic-requests-only/99573-inspiron-15-5510-5518-boardview-schematic?p=1843442#post1843442"]the boardview for the 15 5510[/URL]… They are just the same. However, it looks like mirrored in OpenBoardView/FlexBV.I had a 15 5515 for repair this week, and looked at [URL="https://www.badcaps.net/forum/troubleshooting-hardware-devices-and-electronics-theory/troubleshooting-laptops-tablets-and-mobile-devices/schematic-requests-only/99573-inspiron-15-5510-5518-boardview-schematic?p=1843442#post1843442"]the
-
For what it's worth, it seems to match the Inspiron 15 5515 as well, though it looks like mirrored in OpenBoardView & FlexBV for some reason.
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
I know about Hachoir : [url]http://hachoir.readthedocs.io/[/url]
Didn't use it much, and it doesn't run for some reason from the package here.Re: WANTED: Teboview / TVW file form... package here.Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
I know
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
We'll soon have to open some champ I guess.
On the topic of other formats, yesterday I had a look at Sprint Layout (another night not slept) because people recreating all those old computer PCBs mostly use that, it seems [URL="https://github.com/sergey-raevskiy/xlay"]someone started REing[/URL] that (but it's some win32 stuff that doesn't even builds with libwine because MFC). Would be nice to get proper board view when troubleshooting battery-damaged logicboards like the...
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
Oddly the Gigabyte file didn't open in TeboView 4 even after stripping the password… But forcing the previous string to "G34…" stopped it from complaining about license :-)
Opened a PR with a python tool to strip the password.
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
Great, let me know if you need more.
Yeah, mingw works not too bad, I recall building VLC with it (quite slow though).
I think most of build.sh can probably be done right in CMake though.
Yes, it's a classic idom to detect the number of cores to do parallel builds, except it's very Linux-specific while there's a much simpler and portable method. I fixed this in MuseScore some years ago. I already proposed a patch...
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
So yeah, with [URL="https://github.com/mmuman/teboviewformat/blob/f5af896402d45a95a430ee96a6017827b124bebf/dump_tvw.py"]the current python code[/URL]:
cds2f_NSA911R0-0329.tvw seems to decode (but the next thing is unknown, so maybe…)
NSB241R10.tvw decodes but it only has one surface on the first layer.
cds2f_NSA912R10-0329.tvw fails to decode at the second Surface because there's an extra 4 bytes before the net ID:
[CODE]== 2...
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
Yeah that's a list of pad/lines/whatever, with the number of entries, some unknown uint32, then the net, the d-code id (starts at 10), then coordinates…
I'll start writing that up, but I must post the retrocomputing devroom request for FOSDEM first before tomorrow :-)
Leave a comment:
-
Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder
Ah cool.
Last night I managed to parse the first layer of NSB241R10.tvw until the next one.
Still not sure what the first int after the colors are, but after the D-code definitions (ended abruptly with 0,1 as w,h) are listed the pads, lines, surfaces… with a count and the content if count isn't 0.
Leave a comment:
No activity results to display
Show More
Leave a comment: