Raspberry pi 3 hanging on serial print about circle HOT 4 CLOSED

You only need to go to the Circle boot/ directory and do make there to get the most recent firmware from here. Please copy the files bootcode.bin, start.elf and fixup.dat to a uSD card along with the kernel image file.

If you want to get output to the serial interface on GPIO 14/15, you need to create a file cmdline.txt on the uSD card, which has this contents:

logdev=ttyS1

I append a kernel image of sample/04-timer, which has been successfully tested with the firmware of today on a RPi 3 v1.2.

kernel8-32.img.zip

from circle.

Thank you a lot for your fast response. It was the missing cmdline.txt. it worked like a charm.
Also, i tested the fractal, mandrelset sample, and it worked very well. Although, when reading the code from kernel.cpp

it initializes mandrelset class like this:

TShutdownMode CKernel::Run (void)
{
	m_Logger.Write (FromKernel, LogNotice, "Compile time: " __DATE__ " " __TIME__);

	m_Mandelbrot.Run (0);

	return ShutdownHalt;
}

But, if mandrelset receives an first argument that corresponds to each core number, how this constant "zero" be different for each core instance?

from circle.

There is a different initialization for core 0 and core 1-3. Core 0 is started at 0x8000 by the firmware and is directed to CKernel::Initialize() and then to CKernel::Run() by the Circle sysinit code. The secondary cores 1-3 are parked in a loop after boot by the firmware and will be released from that loop in CMultiCoreSupport::Initialize() which is called in CKernel::Initialize(), because the class CMandelbrotCalculator is derived from CMultiCoreSupport.

The secondary cores then jump to CMultiCoreSupport::EntrySecondary and in line 185 to this Run() routine for each secondary core. Because core 0 has its own initialization path, it explicitly calls CMandelbrotCalculator::Run() with its core number 0. So the execution of all cores reaches CMandelbrotCalculator::Run() in the end.

from circle.

Thank you so much @rsta2, i'm working with circle to provide a wrap around arduino. I've already manage to modify a bootloader from dwelch67 and included a python script to automate flashing (Takes me around just 1 sec for flashing the 01-blink example with a baud rate of 1M). I'm looking forward to contribute with this project. As a windows user, I wouldn't be more happier to see this project running out of the box with arduino IDE. And is totally possible to maintain the native libraries without compromising flexibility.

from circle.