A newcomer asks about Riotboard HDMI...

Hello .

Well I got the HDMI to VGA cable today. (As mentioned above..)

Plugged it into the HDMI connector of the board and plugged a dell LCD monitor into the VGA end of the adapter...

Turned on the board and!!!!!

NOTHING!!!

I also tried plugging it into my laptop VGA socket. The laptop screen border changes but TIA... hmmm....

Anyone have any ideas or experience of what I can do?

(apart from spending hundreds of punds on something I don't have the moolah for at the moment...?)

Cheers,

Steve.

plugged a dell LCD monitor into the VGA end of the adapter

HDMI interfaces are highly supported but with vga connectors may not work.

apart from spending hundreds of pounds ...

serial console is nice and good if there is no display specfic work.

I mentioned the software setup here and hardware connection here.

Hope that helps for the moment.

Yes but 45 minutes for Python is really long.

Even on the RaspberryPi that compiles a lot slower than the RIoTBoard it doesn´t take that long.

I´ll install the Image on my RIoTBoard and will look if I can reproduce the problem.

OK. The time and date on my board was set to 1970... I kept getting a message during the compile about some process or other being in 2012...

I've updated the time to now and tried make again,

now i'm getting stuff like this:

gcc -pthread -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes    -I. -I./Include    -DPy_BUILD_CORE -o Objects/bytearrayobject.o Objects/bytearrayobject.c

which looks more promising,,,

its been running for about 45 minutes now... should it be taking this long????

should take that long, may be it has something to do with the eMMC latency.

did you try using apt-get, i guess 2.7 based armel packages will be available.

Yup that´s looking good the compiler actually compiles something now.

Even i want to give it a try and check if its that slow .

I am away so can't do it now.

to keep away the time stuff set your clock to current time using below

date +%Y%m%d -s "20140526"

date +T -s "23:55:00"

this will set the clock and hopefully not give any future date warnings  or annoying 1970s stuff.

ooh! ooh! update!! make has finished so I've now executed sudo make install...

now thats going ahead... could it have been something to do with the time and date setting?

if so, I'd have been waiting 42 or so years for it to finish.

42 years ago the first microcontroller was being developed as a calculator on a chip!! 

thats great it compiled, i guess no more hurdles ahead.

. could it have been something to do with the time and date setting?

the make has nothing to do with time, not really.

even with "time in future.." warning which some time shows during package (build/install) i have managed to build and install some packages in Rpi long back.

but it looks annoying, so to shoo them off I just put it above .

just trying to help, if i can

42 years ago the first microcontroller was being developed as a calculator on a chip!! 

hopefully today some micro controllers are capable  of running python.

i never tried it, but some "micropython" exists out there.

steven scutt wrote:

 

OK. The time and date on my board was set to 1970... I kept getting a message during the compile about some process or other being in 2012...

Ah yes... various things stupidly check the clock and then fail to compile if the data/time is prior to the date/time the sourcecode was released... sane stuff uses relative changes in time from when you start the compile. You might end up needlessly compiling some extra stuff if the clock is in the past, but rather than failing it does actually work..

What you've seen is a case where some sub-project is continually referenced and each time it is it thinks something is 'wrong' and either rebuilds the whole thing every time or just fails at the ./configure step. configure can take a while itself, so what looks like a loop might either eventually finish successfully, or eventually fail.

Moral of the story: Set the clock before you start!

steven scutt wrote:

 

OK. The time and date on my board was set to 1970... I kept getting a message during the compile about some process or other being in 2012...

Ah yes... various things stupidly check the clock and then fail to compile if the data/time is prior to the date/time the sourcecode was released... sane stuff uses relative changes in time from when you start the compile. You might end up needlessly compiling some extra stuff if the clock is in the past, but rather than failing it does actually work..

What you've seen is a case where some sub-project is continually referenced and each time it is it thinks something is 'wrong' and either rebuilds the whole thing every time or just fails at the ./configure step. configure can take a while itself, so what looks like a loop might either eventually finish successfully, or eventually fail.

Moral of the story: Set the clock before you start!