Evaluation Type: Independent Products
Did you receive all parts the manufacturer stated would be included in the package?: True
What other parts do you consider comparable to this product?: TBC
What were the biggest problems encountered?: Lack of available information, but that's what this review aims to provide :)
08:22 AM, 10 October 2004
I have successfully installed Linux Debian on the board and am trying to get the framebuffer working.
I believe the issues I am having are caused by the onboard power regulator, an act8865 power regulator that uses i2c to communicate with the host board and causes device contention.
To get to the same stage I am at currently follow the guide at https://eewiki.net/display/linuxonarm/ATSAMA5D3+Xplained
When running with the debian image you get a nice startup screen, I have also edited the file atmel.bmp and added custom strings to the startup page.
To get wifi working, when doing the build-kernel step:
[*] Networking support -> Wireless -> [*] cfg80211 wireless extensions compatibility
2:27 AM, 27 September 2014
I have the frame buffer working in a fashion, I can display RGB565 images (currently upside down and back to front but it is a massive start!)
This is a placeholder for my review and will change as the review progresses.
The board works in linux and appears on my system as
when plugged in via the micro USB port.
When plugging in via network, the device can get its own IP address using DHCP. Be aware that the MAC address changes at each reboot to a random address. You could (possibly) fix this using /etc/network/interfaces
The blue flashing light will rapidly become little more than an annoyance. Luckily we can log into the board using SSH over the network or the micro USB port using a serial terminal program such as putty or minicom.
To turn the blue LED off, type in the following:
echo none > /sys/class/leds/d2/trigger
To see what else the LED will automatically flash to, type in the following:
which will give the following list:
none nand-disk timer [heartbeat] gpio mmc0 mmc1
By default, the trigger is heartbeat which pulses like a well, pulse.
none means the light does not flash
nand-disk happens whenever the internal NAND memory is accessed
timer flashes once a second
heartbeat pulses like a heart
gpio flashes whenever a GPIO port is accessed
mmc0 flashes whenever the bottom SD card slot is accessed
mmc1 flashes whenever the optional top SD card slot is accessed
Hi, I have a problem with your same board-kit...what you have do to have the LCD working?
I had flash the system image with demo_linux_nandflash_pda4.bat and connect the LCD as you can view in the photo...what is the problem? I have to do a configuration o run a process to have the LCD working and test it?
Thanks in advance
To enable the frame buffer I installed a demo firmware.
The (very delicate!) cables go:
lcd -> interface board, blue side facing towards you
interface board -> xplained, blue side facing towards PCB
Why they didn't stick to the same headers all the way through escapes me.
Can you share how you got the frame buffer to start working
also is the cables flipped over into the main board from the LCD, it looks that way from the photo, also looking at the display it looks like pin one is on oposit sides of the board