| --- Log opened Sun Feb 19 00:00:07 2017 | ||
| psychotrope | okay so I'm beginning to think I'm in a bit over my head, here is my current situation for those interested / want to help: | 02:30 |
|---|---|---|
| psychotrope | I want to run an openRISC core on a DE0-Nano board, and then run linux on that | 02:30 |
| psychotrope | I would like to compile GPG from source for openRISC once I have linux installed | 02:31 |
| psychotrope | now the hard part, the DE0-Nano has no large built in storage, how would I best be able to boot the system without having to load everything from a linux PC at boot | 02:31 |
| psychotrope | all the need is serial IO for those who mentioned it earlier, I will be using a parallax propellor to interact over serial with the busybox shell | 02:32 |
| psychotrope | so in short: can I compile GPG on openrisc, and can I run the system independent from a PC | 02:33 |
| psychotrope | thanks to all who helped :) | 02:33 |
| psychotrope | oh and congrats olofk | 02:33 |
| shorne_ | psychotrope: Would you be ok to build GPG on our desktop then package and send it to the de0 nano? | 02:52 |
| -!- shorne_ is now known as shorne | 02:52 | |
| olofk | psychotrope: Yeah. As shorne said, cross-compiling on your PC would be the recommended way to do it. There's a SPI Flash on the board, and that will fit a compiled Linux system fine | 11:29 |
| psychotrope | so build GPG directly into the Linux install rather than installing it afterwards? I don't see why that would be a problem at all. olofk: I didn't know the spi flash onboard was enough to handle a full linux install | 12:45 |
| psychotrope | sorry if I sound like a total noob here | 12:46 |
| psychotrope | I don't care how I have to get it working | 12:52 |
| psychotrope | I'd just really like the boot up my openRISC system anywhere and have access to GPG tools | 12:52 |
| psychotrope | reading and writing to an SD card for data tranfer would also be great; don't know how I'd implement that though | 12:53 |
| psychotrope | I need some way to transfer data to and from the DE0-nano, and I'm using the serial connection for connecting the parallax propellor | 12:54 |
| -!- ZipCPU|Laptop_ is now known as ZipCPU|Laptop | 15:58 | |
| olofk | psychotrope: Just ask away. That's how we learn new stuff :) | 17:08 |
| olofk | psychotrope: Until you have a running system in your SPI Flash, you will use JTAG to get stuff to the board | 17:08 |
| olofk | So you first program the FPGA via JTAG | 17:09 |
| olofk | With the FPGA programmed, the OpenRISC CPU and the debug system will be running, so now you connect to the debug system through JTAG. That way you can upload your software (Linux kernel + userspace) directly to RAM and start executing | 17:10 |
| olofk | Once you have a linux image that you're happy with, you can create a image file with the FPGA + Linux and program that to the onboard Flash. | 17:11 |
| olofk | From then on, when the board is powered up, the FPGA will automatically load from the Flash, and when the CPU is started, it will load the software from Flash to RAM, and you got a running Linux system that you can connect to through UART | 17:12 |
| psychotrope | olofk: how much space is there in the Flash on the DE0-nano. I didn't see it listed anywhere | 17:47 |
| psychotrope | I'm concerned that GPG will be too big to fit along with linux kernel in the flash | 17:47 |
| psychotrope | also, what does a bigger FPGA get me with openRISC? More cores? | 17:48 |
| psychotrope | I assume the images found here: : https://github.com/openrisc/orpsoc-cores/tree/master/systems are purpose built for each chip and use more of the FPGA than on the smaller boards | 17:49 |
| -!- ZipCPU_ is now known as ZipCPU | 19:56 | |
| --- Log closed Mon Feb 20 00:00:08 2017 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!