Hi
when I try to import an eagle XML file I get the following error:
This file comes from TI WEBENCH, and when I inspect it, it is clearly XML formatted. I can not upload the file to this forum because I am new to this forum, and it does not allow me to upload files.
Can someone help me resolve this problem?
Kr
Bram Breda
2025-10-18_07-28-35.sch (62.2 KB)
You can upload it now
I get the same error as reported here using KiCad 9.0.5 under Kubuntu Linux.
Attempting to open this file using the last night’s Nightly (9.99.0-unknown-cf0adbb1dc~186~ubuntu24.04.1) gives the same error, then the application crashes with a Segmentation Fault.
The file is internally labeled as being from Eagle 6.1. Eagle 7.7.0 has no trouble opening the file and displaying the schematic. Saving the file using “Save as” produces a file that KiCad 9.0.5 opens, though it’s not the greatest import. Sadly, the Nightly crashes attempting to open this file too.
I’ve attached the re-saved file here: 2025-10-18_07-28-35-resaved.sch (59.6 KB)
So what’s the difference in the files? Firstly, this file is missing the xml version and doctype tags at the start of the file. These should look something like this (from an actual Eagle 6.2 schematic):
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE eagle SYSTEM "eagle.dtd">
Adding these headers got me past the initial KiCad error message, but then KiCad complains it can’t open the file. I got past that by inserting line breaks between each of the XML tags, which are missing from the original file.
This allowed KiCad to read the file, but it issued warnings missing info. I suspect some of the line breaks split tag closings from the data it enclosed, altering its interpretation.
Even though this Eagle schematic is corrupt (lacking essential tags), I think a proper bug report is in order here.
I get the same results. Importing the original upload does not work. KiCad complains with: 2025…sch is an Eagle binary format file"
Importing the re-saved file works on KiCad V8.0.9 and I see something resembling a schematic. Resistors and capacitors with values, but for the IC (U1, TPS43061RTER) all the pins are “mirrored” with the pin labels on the outside of the rectangular box.
That explains things a bit.
It is quite likely that the file is not a valid Eagle format file as the 3rd party TI tool created it.
KiCad should start giving segmentation faults.
I’m guessing this is a typo that was intended to read:
KiCad should not start giving segmentation faults.
Indeed. From what I understand, best practice is to have solid code that verifies all input during reading. And as a safety net you can wrap an exception around that, and throw an error for the file reading bit, but continue with KiCad after disregarding all the read file stuff, so at least you don’t loose unsaved stuff. Best I know, segmentation faults are always programming bugs, but I have never done much PC programming.
I’m a software engineer with over 40 years experience writing code that went into everything from TCP/IP stacks to process control systems. Unhandled exceptions are always an error on the programmer’s part.
As I explained to some of the seminars I gave, “You don’t three-finger-salute a steel mill. Crashes cost millions of dollars and may kill people.”
The rule when developing applications was to be liberal in what you’ll accept and be strict about what you produce.