Posts by RSchubert

Hello,

how do I set video output to HDMI with the standard linux kernel / rootfs?

I tried to add following to the bootargs:

but the efus is always booting with a standard set 800x480 LCD display. So how can I change display settings?

Here's my Kernel Command Line:

Here's my fbset --info:

I tried to find out some more. Here is what the kernel log is displaying:

I guess HDMI is enabled in kernel. These related files are compiled:

drivers/video/mxc_hdmi.c
drivers/video/mxc\ldb.c
drivers/video/mxc\mxc_dispdrv.c
drivers/video/mxc\mxc_dvi.c
drivers/video/mxc\mxc_edid.c
drivers/video/mxc\mxc_ipuv3_fb.c
drivers/video/mxc\mxc_lcdif.c

Any suggestions what's wrong? Help is needed please.

Thanks for answers.

As I see the HUSH shell is not enabled in the Multiplatform 2.0 u-boot. So it's not possible to do conditional scripting while booting. I tried to enbale the CONFIG_SYS_HUSH_PARSER in u-boot. Now conditional scripting is working but I'm not able to mount my UBI filesystem from kernel. The kernel does not find any ubi partition. If I'm using the u-boot without HUSH it's working again. The kernel commandline with the bootargs seems to be the same. So I guess it's because of interpreting some variables. The $(varname) is not working anymore. I had to substitude into $varname but there must be something else I do not find.

Thanks for any advice.

Dear support-team,

We have more and more PicoMOD7 with broken kernel. I found out a little more what's wrong with the devices. They all have 1 to 3 bit errors when reading back the kernel into RAM. These bit errors are addressed randomly over the whole 2.8 MB and different on all devices. All bit errors have in common, that a bit that should be 0 is read as 1. So there are bytes that changed from 0xCA to 0xDA, 0x6C to 0x6D, 0x32 to 0x33, 0x73 to 0x77, 0x89 to 0x8B and so on. In every faulty device I found 1 to 3 such errors. These devices are working for weeks until this happens. If I reload the kernel or even only "repair" the broken bytes the devices are running for weeks again. The kernel is partitioned read only in u-boot env (see above). Is it possible that there's a problem in the NAND ECC or bad sector handling? All devices are showing me 0 bad sectors with "nand bad". I'm using the "u-boot-2012.07-f+s-V2.0".

This is a serious problem for us.

Thanks for any help.

Today I tried once again to double check and got the following result (I used different addresses):

[IMG:http://www.passtec.de/tmdownload/kernel2.png]

There seems to be a difference in the files. Is it possible to write the nand kernel with tftp? So it's more easy to find differences.

Here my uboot environment:

[IMG:http://www.passtec.de/tmdownload/env.png]

URGENT !

Once again we have a device where the kernel does not start (see above).

Now I tried to check the kernel with following result:

[IMG:http://www.passtec.de/tmdownload/kernel.png]

The content of the nand seems to be the same as the original kernel file.

If I load the kernel to address 40800000 and run bootz the kernel is starting. If I load from nand it is not starting. I would not believe if I would not have seen it myself.

is working

The kernel is not running although the content seems to be the same.

What can I do? Urgent help needed! We get back one device after another from our customers!

Thanks in advance

I will do this if it happens the next time. For now I reloaded the kernel and it's working again without problems. I will let you know if there's something new.

The u-boot was compiled from original sources "u-boot-2012.07-f+s-V2.0". So I think it's V2.0 already.

In difference to the problem on armstoneA8 I have no line "Uncompressing Linux... done, booting the kernel."

The kernel file size is 2.841.168 bytes (below 3MB).

We also thought of ESD problems when touching the housing where the Picomod is assembled. But we double checked that there's no electrical connection between housing and Picomod.

Would be interesting for us too.

Dear Support-Team,

we're using the PicoMod7A with kernel 3.3.7 and u-boot 2012.07.

On three different of about 20 devices (until now) we had the problem, that after a long time (2-3 months) of running without problems the kernel got broken. The devices are crashing and aren't booting any more. When I connect the debug port (COM3) I see:

and nothing more happens. It seems the kernel is copied into RAM, is executed but contains invalid code so nothing happens. After I reload the kernel and FFS from SD-Card everything is working correctly again.

In the bootargs the kernel is write protected "3m(Kernel)ro,-TargetFS". So I hope it will be impossible to cause overwriting parts of the kernel from an application running in the buildroot FFS.

Can you give us any advice why this is happening? Where can we start isolating the problem?

Thanks in advance

Dear F&S Team,

in the UBootEnv there are some ethernet settings for booting via nfs (ipaddr, serverip, gatewayip, netmask). My question: are these values used when booting from flash (bootubi)? The reason of this questions is: if the device is booting with these ip address set - this may cause an address conflict if another device in the network has the same address. Even if the boot sequence is very short. In my /etc/network/interfaces I use the 127.0.0.1 IP for loop back and set the device IP (user settings) later in my firmware.

Thanks for answering.

Dear F&S Support team,

what about the plans allocating the display framebuffer in U-Boot because of the paging problem for high display resolutions? Is there a timetable for a next Linux multiplatform release? What are the next things to be added/changed?

RSchubert

Dear support team,

how can I control direction and value of the PicoMODs7A GPIOs in Kernel. The reason is we're using a beeper/buzzer on GPIO8. While uboot is running the output is low (beeper off). While Kernel is starting the output is high or connected as input (beeper off). In the rootfs I hav full control over the GPIO. So the questions is how to get control over the GPIOs in Kernel and if possible in uboot.

Thanks for answers

No ideas how to access COM1 ??

Debugging seems to work well now with the 4.7.2 toolchain. But I still have problems with the new toolchain and buildroot.
http://www.forum.fs-net.de/viewtopic.php?f=23&t=3380

Thanks...

Buildroot-2012.11 is not working because of the same problems.

Buildroot-2013.02-rc2 is seems to work. I copied the board/f+s directory and the /config/picomod* files to the new buildroot and configured with the picomod_def_config. I get the image files and all the needed libriaries but I don't know if there are some more special changes/settings in buildroot made by F+S.

Kind regards

Added:

In buildroot-2013.02-rc2 I don't get the initial console working. I see all the information while booting but the login is not running on this serial port. What buildroot version is F+S using together with the new toolchain??

As I found in the web the problem seems to be in the gdb sources:
http://patches.openembedded.org/patch/31227/
Is there a newer F+S version of buildroot that fixes such things ?

Thanks for answers.

Error while compiling the Buildroot-2012.08-f+s-V2.0 with the new toolchain.

Also when I disable the GDB in the buildroot configuration the compiler stops with an "incomplete type" error (but in a different file with a different type).

I dont have the CTNG_LD_IS variable set.

Compiling with the 4.6.3 toolchain always was working without errors.

Thanks for advice.

I cannot acces COM1 (Starterboard) with Picomod7A.

COM3 can be accessed on /dev/ttySAC2

for COM1 I tried /dev/ttySAC0 and /dev/ttySAC1 but I get no communication.

Thanks for any hints.

Dear support-team,

I need to set a custom baudrate to the serial port. I try this with the following code:

When I run the program the first time it's killed in the

command with the message "... sets custom speed on ttySAC1. This is deprecated".

The BaudBase and the Divisor will be printed with value 0. When I run the program a second time this seems to work. Baudbase and Divisor will be printed as 300000 and 6. The program will not be killed.

Why does'nt this work when running the first time? Is this the right way to set a custom baud rate?

On PicoMod7 with kernel 2.6.39 it was not possible to set a custom speed this way. I had to run a module where I could access a special register in "PHKMEM":

But that was not very comfortable.

Thanks for any hints.

Any news about this problem? Using uclib is no option for me because threads are not working as expected there.

Thanks for answers.