32 bit version might have problems with timestamps created by 64 bit version
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| KiCad |
Fix Released
|
High
|
jean-pierre charras | ||
Bug Description
Investigating the bug of https:/
There is either something wrong with that project that only 32 bit versions find or 32 bit versions have a problem with timestamps created by 64 bit versions.
Error message of 32 bit version:
Error loading schematic file “E:\Mes documents\
invalid hexadecimal number in input/source
“E:\Mes documents\
line 7277, offset 6
---
Line 7277 of the file is
U 1 0 8860D03359D6C4F2
which is part of the component
$Comp
L V_Custom:Crystal Y1
U 1 0 8860D03359D6C4F2
P 8500 2650
F 0 “Y1” V 8200 2600 59 0000 L BNN
F 1 “16Mhz” V 8100 2500 59 0000 L BNN
F 2 “CRYSTAL” H 8500 2650 50 0001 C CNN
F 3 “” H 8500 2650 50 0001 C CNN
1 8500 2650
0 -1 -1 0
$EndComp
File is already on launchpad https:/
| Changed in kicad: | |
| importance: | Undecided → Critical |
| importance: | Critical → High |
| milestone: | none → 5.1.1 |
| Rene Poeschl (poeschlr) wrote | #1 |
| KiCad Janitor (kicad-janitor) wrote | #2 |
| Changed in kicad: | |
| status: | New → Fix Committed |
| assignee: | nobody → jean-pierre charras (jp-charras) |
| Changed in kicad: | |
| status: | Fix Committed → Fix Released |
It might be that even 64 bit eeschema has problems with such timestamps and that this is the reason for the connected bugreport.
The user created a new schematic where they do not experience the same trouble. The main noticeable difference is the timestamps in that new schematic are 8 hex digits (=32 bit) long instead of 16 digits (=64 bits).