Just open another command prompt? I’m not exactly sure what you are doing… is this on Windows of RasPi? I have a raspi in a drawer somewhere… waiting to do something cool with it
@kennethlimcp, You can use screen (sudo apt-get install screen) to launch a separate terminal process on the Raspberry Pi to let something run in the background. There are a ton of options for it, but the basics are:
On a command line, type screen and press enter.
Press spacebar or enter to continue past the warning/disclaimer screen
You should now be presented with an empty terminal, which now means you are in the new terminal process. Type whatever command you want to have running in the background.
Press ctrl+a then d to exit the screen while leaving it running in the background.
Type screen -r to resume that screen session.
Press ctrl+d to log out of the screen session when you’re done.
It is especially useful for the Raspberry Pi since it’s really, really slow. I’m using it now to compile Node.JS on a Raspberry Pi (to set up the local cloud and Phant). Hopefully I can get another port in our data center and to put the RPi on it and have a public IP (instead of this LAN/firewall nonsense).
Also, I’m on the list for hummingboard (solid-run.org) and will receive one the moment they ship! You might want to consider that in future since it’s more scalable and using vanilla linux.
Will do up a tutorial for that the moment I have it.
I have an Odroid U3 at home that I use for my 3D printer. The RPi couldn’t keep up and would cause prints to lock up for several seconds at a time. I want to get my hands on as many computer-on-a-board products as I can (CuBox, Parallella, Udoo, etc) and put them through their paces. I’d also like to have the extra cash to spend on them as well!
I did all the steps, but the core is just fast blinking with white colour, also on the terminal window the core is not appearing.
At this step:
7.) Go to cores_key directory to place core public key inside
cd core_keys
place core in DFU-mode
spark keys save INPUT_CORE_ID_HERE NOTE: make sure you use theCORE ID` when saving the keys!
Reset the core manually by hitting the RST button
It was a bit confusing for me because the core_keys folder is on the server, but the spark keys save… command has been run on my local machine. It saved a file, and i manually copied the generated file to the server’s core_keys folder. Maybe that should be done on another way, not sure, but at the moment it is not working
If anyone has a solution please let me know, this would be ace to run the cores from a local environment.
spark keys save will copy the raw private key in DER format and the wrong size from the core, and the server needs the public core key in PEM format, no?