First thing to check is probably that your dip switches are correctly set.
Seem to recall my DE0 board arrived with them in FPGA programming mode
positions
On 08/02/2018 05:09, mugginsac wrote:
Thanks Schooner and Michael,
I followed the instructions through the setenv default -a; setenv
Thanks Schooner and Michael,
I followed the instructions through the setenv default -a; setenv ethaddr
ba:d0:4a:9c:4e:ce; saveenv; reset.
Now I get a little farther. Do I need to remove the 'quiet' in
extlinux.conf following the 'rootwait' so that I can see what is going on
in the starting
On 07/02/18 07:03,
'schoone...@btinternet.com' via Machinekit wrote:
Read the gist that Michael did for the DE0
Specifically here
https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337
where you will see exactly the
Read the gist that Michael did for the DE0
There is a link to it in the blogs.
You have to set the NIC MAC address etc and then restart
On 06/02/2018 23:54, mugginsac wrote:
I finally got the USB console working under stretch.
I didn't have the dtb file that it was looking
I finally got the USB console working under stretch.
I didn't have the dtb file that it was looking
(socfpga_cyclone5_de10_nano.dtb) for in the boot/dtbs/4.9.68-socfpga-r3/
directory.
After I fixed that it is either loading the kernel or trying to load the
kernel. It is getting a crc error and
On 1/30/2018 12:56 PM, mugginsac wrote:
> Charles,
>
> Robert’s instructions only create two partitions, an A2 and an EXT4.
> The “A2” partition is where u-boot-with-spl.sfp gets written.
> The ext4 partition is for linux. The kernel resides in the “boot” directory
> along with a directory
Charles,
Robert’s instructions only create two partitions, an A2 and an EXT4.
The “A2” partition is where u-boot-with-spl.sfp gets written.
The ext4 partition is for linux. The kernel resides in the “boot” directory
along with a directory for the extlinux.conf file, and a directory for the
On 1/28/2018 5:58 PM, mugginsac wrote:
> I am trying to follow Robert Nelson's instructions on the eewiki to build a
> stretch installation for the DE10-Nano with a DE10-Nano-DB25 and 1206 size
> parts.
>
> I got u-boot built from the github repository but it still won't boot. My
> guess is
I am trying to follow Robert Nelson's instructions on the eewiki to build a
stretch installation for the DE10-Nano with a DE10-Nano-DB25 and 1206 size
parts.
I got u-boot built from the github repository but it still won't boot. My
guess is that the FPGA is not properly initialized. So my
What Quartus version ?
I have 15.1,16.1 and 17.0 running in Stretch only problem I have had is
that it crashes when setting the license variable on first run.
My strategy is to use the native (mostly qt) lib versions instead of the
ones in the quartus/linux64 folder renaming like this:
I am in the process of downgrading from Stretch to Jessie. I couldn't get
Quartus to run on Stretch. It needs libpng12.0 and the notes I found about
it and Stretch said that Stretch won't allow you to load libpng12.0 that
you have to go to libpng14 or libpng16. Libpng16 is preinstalled on
I understand CONFIG_DEFAULT_FDT_FILE but what does
CONFIG_DEFAULT_DEVICE_TREE indicate?
CONFIG_DEFAULT_DEVICE_TREE="socfpga_cyclone5_de10_nano"
CONFIG_DEFAULT_FDT_FILE="socfpga_cyclone5_de10_nano.dtb"
The DE10_NANO_SoC_GHRD *(Golden Hardware Reference Design) from the
DE10-Nano CD uses
Is there a way to get the DE10 to use uenv.txt for boot environment info
with the new u-boot?
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit"
When I boot the disk that has the original boot loader. I get the following:
UART clock 10 KHz
CLOCK: MMC clock 5 KHz
CLOCK: QSPI clock 3125 KHz
RESET: COLD
SDRAM: Initializing MMR registers
SDRAM: Calibrating PHY
SEQ.C: Preparing to start memory calibration
U-Boot SPL 2013.01.01
On Thu, Aug 24, 2017 at 3:51 PM, mugginsac wrote:
> OK that made some progress. It still looks like some command processor is
> running at the same time as the login process.
>
> It printed "U-Boot SPL 2017.05-dirty (Aug 23 2017 - 15:20:51)
> drivers/ddr/alt" on the serial
On 8/24/2017 3:51 PM, mugginsac wrote:
> OK that made some progress. It still looks like some command processor is
> running at the same time as the login process.
>
> It printed "U-Boot SPL 2017.05-dirty (Aug 23 2017 - 15:20:51)
> drivers/ddr/alt" on the serial console and then went quiet. Next
OK that made some progress. It still looks like some command processor is
running at the same time as the login process.
It printed "U-Boot SPL 2017.05-dirty (Aug 23 2017 - 15:20:51)
drivers/ddr/alt" on the serial console and then went quiet. Next thing I
saw was that it had apparently loaded
On Wed, Aug 23, 2017 at 10:56 PM, mugginsac wrote:
> I still have problems with the serial terminal.
>
> It seems to me like U-boot is starting up and receiving input that is
> putting it into command mode. Then it is like the process that outputs the
> text from the DE10 is
I still have problems with the serial terminal.
It seems to me like U-boot is starting up and receiving input that is
putting it into command mode. Then it is like the process that outputs the
text from the DE10 is being fed into the console input and confusing the
heck out of the command
Robert,
Thanks. At least it loaded right up as shown on the serial terminal. Now it
is at least looking for the ext4 filesystem before loading the ext2
filesystem.
Something that I read suggested that the journal-ing stuff on ext4 could
shorten the life of the uSD card but that the ext4 has
On Mon, Aug 21, 2017 at 4:56 PM, mugginsac wrote:
> Here is what I am getting from trying to boot the uSD I built. Is it
> possible that I have a bad uSD?
>
> U-Boot SPL 2017.05 (Aug 20 2017 - 08:57:37)
> drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
>
On 8/21/2017 5:59 PM, mugginsac wrote:
> Charles,
>
> What terminal software are you using?
> Is there any special setup required other than 115,200 baud and 8N1
> (data,parity, and stop bits)?
> I can't get putty to work with the DE10 and I sometimes get those weird
> single column scroll down
Charles,
What terminal software are you using?
Is there any special setup required other than 115,200 baud and 8N1
(data,parity, and stop bits)?
I can't get putty to work with the DE10 and I sometimes get those weird
single column scroll down the right hand side with minicom.
Alan
--
On 8/21/2017 4:56 PM, mugginsac wrote:
> Here is what I am getting from trying to boot the uSD I built. Is it
> possible that I have a bad uSD?
Your uSD is probably fine.
There's a CRC error because you don't (yet) have a saved U-Boot
environment on the A2 partition. Based on the output you
Here is what I am getting from trying to boot the uSD I built. Is it
possible that I have a bad uSD?
U-Boot SPL 2017.05 (Aug 20 2017 - 08:57:37)
drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
Taking a break from watching the progress of the solar eclipse.
What I am trying to do is get to the point of building a system that will
run with HDMI before I start trying to add MachineKit and the hm2 stuff.
At the moment the build doesn't seem to run HDMI. I thought I was using the
same
I rebuilt the uSD with an ext2 filesystem.
At first I got a bunch of messages related to the initialization. Then a
bunch of characters seem to scroll down the right side of the "terminal"
screen in a single column.
Then after awhile, I got a login prompt in minicom, but I couldn't get it
to
On 8/20/2017 6:38 PM, mugginsac wrote:
> OK, my face is red. Yes I was plugging into the wrong port. It is running
> u-boot-with-spl but it is looking for an ext2 partition instead of an ext4.
> So
> after a while it starts looking for a USB device.
With the three different USB ports, it's
OK, my face is red. Yes I was plugging into the wrong port. It is running
u-boot-with-spl but it is looking for an ext2 partition instead of an ext4.
So after a while it starts looking for a USB device.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
On 8/20/2017 4:35 PM, Charles Steinkuehler wrote:
> On 8/20/2017 4:03 PM, mugginsac wrote:
>> Well it appears that the not so fun situation is the case. When I unplug
>> power
>> from the DE10-Nano the ftdi chip disappears. I also tried plugging DE10
>> cable
>> into a powered hub instead of
On 8/20/2017 4:03 PM, mugginsac wrote:
> Well it appears that the not so fun situation is the case. When I unplug
> power
> from the DE10-Nano the ftdi chip disappears. I also tried plugging DE10 cable
> into a powered hub instead of directly into the desktop box but same result.
>
> How about
Well it appears that the not so fun situation is the case. When I unplug
power from the DE10-Nano the ftdi chip disappears. I also tried plugging
DE10 cable into a powered hub instead of directly into the desktop box but
same result.
How about if I plug in the DE10, get the ttyUSB0 and then
On 8/19/2017 4:51 PM, mugginsac wrote:
> OK, I can now get a /dev/ttyUSB0. I had to add altera vendor id 0x09fb and
> DE10
> product id 0x6810 to ftdi_sio. I have to plug in the USB cable from the DE10
> to
> get ftdi_sio to load. Then by the time I get it plugged in and putty loaded
> there
OK, I can now get a /dev/ttyUSB0. I had to add altera vendor id 0x09fb and
DE10 product id 0x6810 to ftdi_sio. I have to plug in the USB cable from
the DE10 to get ftdi_sio to load. Then by the time I get it plugged in and
putty loaded there is nothing coming over the console. If I try to start
On 18/08/17 05:06, mugginsac wrote:
By the way it with with the USB cable connected to
the D525MW and running lsusb it shows up on bus 2 as device 32
and is correctly identified as Altera (09fb:6810).
But I don't know how to get a
Charles,
I installed putty on my D525MW linux box, and I plugged a USB A to mini
cable from the USB port on the desktop to the UartToUSB connector on the
DE10. However, I don't know what pseudo serial port to watch for the Nano?
Can you tell me how to figure out what /dev/tty device to use
Robert Nelson's instructions don't show creating a FAT partition, just an
A2 partition and an EXT4 partition. If I am reading his instructions
correctly he is writing u-boot-with-spl.sfp in the A2 partition then
creating ext4 file system in the 2nd partition. Then he makes creates the
rootfs
Now I am trying to created a bootable image following Robert Nelson's
instructions. (Whoa is me!) Where does the .rbf file go? In the rootfs or
in the A2 partition?
The u-boot-with-spl.sfp goes in the A2 partition, does it pick up the
kernel from the rootfs partition?
Alan
On Monday, July
Interresting I have not heard that armhf Stretch compatibility is fully up
and working yet so I have been sticking to building jessie images via my
recently updated build script(s).
https://github.com/the-snowwhite/soc-image-buildscripts
please share when you get MK armhf and Debian Stretch to
Charles,
That worked. I now have the DE10-Nano booting into Debian Stretch console.
I just formatted the Angstrom partitition, expanded the partition to fill
the uSD card, made an ext4 partition out of it, and then followed Robert
Nelson's instructions to expand the minfs tar into the
The main pieces that are system specific are the boot loader, the
kernel, and the device tree. If you start with a working DE10 uSD
image you can leave the boot-loader (partition type = A2) and the FAT
partition (kernel and device tree) alone and use rsync (or whatever)
to copy a Debian rootfs to
I seem to have hit a roadblock, maybe it is just my blockhead. The linux
system on the DE10-nano is Angstrom. It doesn't have apt-get, sudo or much
of anything else. I was going to try and copy the appropriate files from
the DE10-Nano Angstrom system to the DE0-Nano-SOC Debian system but I
42 matches
Mail list logo