MKesenheimer / fault-injection-library

Python library to perform fault-injection attacks on microcontrollers
GNU General Public License v3.0
48 stars 12 forks source link

[question] porting to kicad ? #2

Open FabienTregan opened 1 month ago

FabienTregan commented 1 month ago

Hi,

I wanted to try a few modifications on the board[^1], but the files are for Fusion360 for which I do not (and don't plan to) own a license. Would you be interested in porting the project to Kicad ? (I think I can do the job, but have no interest in maintaining a Kicad fork if you prefer Fusion).

[^1]: mainly the possibility to have different voltages for power and glitching, since the CC2510 I play with gives better results when glitching from the 1.8V regulation pins but still need to be power-cycled through the 3V3 pin and use 3V3 for communicating on the debug interface. Also visually indicating that e.g. X2 and X_ANALOG are the same thing

MKesenheimer commented 1 month ago

Hey Fabien, if you are willing to do the work, feel free to do so. I am happy for contributions. I do not use Kicad currently, but if you can port the project to this program, I am open to a change since I am not that happy with Fusion360 regarding to PCB prototyping. Maybe this would be the perfect time to switch gears. To sum up: Thank you for your kind offer to port the project. I would like to maintain the project in Kicad after you ported it ;)

FabienTregan commented 1 month ago

I could not open the .fsch and .fbrd files (eagle crashes on my two computers under linux mint). If you have an option in fusion to export the file to a more standard format (eagle 'old' .sch and .brd ?), I could start from your file instead of redoing from scratch. If you can, just attach the files to this issue and I'll give it a try.

MKesenheimer commented 1 month ago

I added the files *.brd and *.sch to schematics. Let me know if these files formats work.

FabienTregan commented 1 month ago

After a few crashes they seem to be imported fine ! I need to check all the biding between components in schematic and PCB, but that will be way easyer than redoing everything from scratch, thanks !

FabienTregan commented 1 month ago

(I'll try sending a first version during next week)

MKesenheimer commented 1 month ago

That's good news. Looking forward to your PR.

FabienTregan commented 1 month ago

On component is present twice on the schematic with the same reference (because x-glitch is automatically numbered as x-glitch0 which already existed) so I renamed this way. Can you confirm it is correct ? image image

MKesenheimer commented 1 month ago

Weird. I do not see the component twice in Fusion360. I double checked and I do not have name collisions.

FabienTregan commented 1 month ago

I don't think the collision is on your side : I think that at import, kicad renamed x_glitch as x_glitch0 which already existed, hence the collision. What I did is I renamed what I think was x_glitch into x_glitch2

MKesenheimer commented 1 month ago

Ah, I see. Yeah, that should be fine I guess.