newaetech / chipwhisperer-vagrant Goto Github PK

Virtualbox settings. Should be an easy fix.

Needed for new testing setup

The most confusing part of getting jupyter up and running seems to be setting the password for jupyter via jupyter notebook password. It would be good to automatically prompt users to set one if there isn't one already set.

When running vagrant up for the first time (aka building the VM) on a slower storage medium (such as a hard drive), vagrant may time out before the VM finishes booting.

According to vagrant, this can be fixed by modifying config.vm.boot_timeout

• Pandoc
• gmpy2

According to this post on the VBox forums, using USB3.0 emulation may provide superior performance to USB2.0 emulation.

It may be worth testing the speeds on both to see if one is faster than the other.

vb.customize ["modifyvm", :id, "--usbxhci", "on"] disables USB2, but leaves USB1 enabled. Appears to be the cause of CWNano issues on VM

This was potentially caused by using the wrong floating point setting for the F3, as it would force the use of full arm instructions instead of thumb, since HW floating point libc didn't exist in thumb until q2-2018 ish. A chipwhisperer patch fixed this, but it'll need to be tested to make sure the issues have the same fix.

Getting the repo on the Windows appends \r to the end of every line. Since we're copying stuff into a Linux environment, we should dos2unix these files to avoid errors when they get parsed in Linux.

Moving the folder or deleting Virtualbox's reference for a VM created with Vagrant causes it to lose the hard drive, preventing the VM from being readded. The hard drive file is still there and the VM can be successfully readded after editing the .vbox file to remove the hard drive. Readding the hard drive file after this seems to fix this.

Need to capture AT91 Bootloader and make sure user is in dialout group