Enchanted Objects: Let's work together to tame the ATMEL SMART SAMA5D4 Xplained Ultra kit

Hi Peter,

you should get the lcd working ok.

You'll need to load it with the relevant config line.

edit the uEnv.txt file and replace this line

fdt_file=/dtbs/at91-sama5d4_xplained_hdmi.dtb

with this line

fdt_file=/dtbs/at91-sama5d4_xplained_pda4.dtb

That should activate the LCD, no kernel compile required.

Accessing the display.. No idea. It probably creates a /dev/xxxxsomething  for the device

Check the directory both before and after  a boot with that line to see what appears in /dev

Regards

Rob

So mine is now printing unreadable text ONLY in the area where the prompt telling me the user name and password, the rest prints perfectly... go figure, and to make things worse I cant remember the loging name or password... Please can you enlighten me

I had spent hours loading GNOME and TIGHTVNCSERVER just to find it is not enough for a remote graphical console but now I cant log in again either without the UNAME and PWD

Thanks

Name: ubuntu

Pwd: temppwd

Clem

Hi Peter,

Was the corruption in the console (via serial port)

or was the corruption on the LCD? ie. was it treating the LCD as a console?

I did have a problem once where I managed to corrupt the SD card while I was experimenting

with the OS builds. I probably popped it in and out once too many times without running

the sync command first.  What it did was corrupt my keyboard so I could no longer type properly..

Regards

Rob

I keep trying to reply via email and its still busted, so you wont have seen my responses

I resolved it by re-loading the SD card. It was only the part at the login prompt where it shows the user name and password, the rest was ok

I am currently trying to get beta MONO 4.0.0 up and running for forms apps, and also some kind of Xserver, no luck so far

Hi Peter,

be interesting to see where the mono 4.0 is failing, is it during the build process?

I assume that it being alpha/beta you have to make it yourself.

I am about to go on two weeks holiday, so won't be able to try anything with the board.

Happy to give the mono build a shot when I get back though.

For X, I got a lot of blank screen greeting me whenever I tried to start it.

I got closer with KDE where I had an actual login prompt on the hdmi screen, but had

trouble after that.  It may have been due to all the messing around I did with settings. So I'll be giving it another

go when I return with a clean setup to see just how far I can get.

I am trying to use the RGB shield on the Xplained board. I2C is connected to I2C-1 which is not in the /dev path. Any Ideas?

I search the net for an answer and will report if I found a solution...

Check the DTB file also known as the device tree binary. If it does not have I2C-1 that would be the problem...

Clem

I am pretty sure I tested devices connected to the I2C bus on the SAMA5D4 without an issue and based on a standard build (Not a custom one) and examples are given right here SAMA5D4 Xplained Ultra - Tips and Tricks #2 - Using the built in IO and external devices

the buss that is set up is '0" and so for example to scan the i2C bus you would issue the command as follows "i2cdetect -y 0"

Hope this helps

Yes, I verifyed that the i2c-0 works. good. moving on to i2c-1 (which is the one broken out on the arduino headers)