Posts by fs-support_AD

Hello,

have you tried a other USB port? Which kind of connection do you mean?
1) PC4 Bootloader (NBoot or Eboot) -> PC
2) PC4 WinCE -> PC

In case 2 you need to install windows mobile device manager.

Hello,

I use both of this tools on my pc with Windows 7 SP1 64-bit and it's work for me. I suppose it is port configuration.

Hello,

maybe blocks windows firewall ports of CEDownloader. First and last ports are 2000 and 2063.
Generaly you can try following steps to download a image.

• In CEDownloader pick needed image file.
• Click on the start button.
• Normaly if port number of CEDownloader is unknown windows will ask you for unblocking.
• Enter 'de' in your terminal in E-Boot menu.
• Now you should see some infos in CEDownloader about your board.
• If automic download is unchecked then use play button to start a download process.

Hope this helps.

Hello,

rgb lcd must be first display (disp0) device mxcfb0 in your settings, because rgb lcd is hardwired to display 0 signals. You can see it e.g. in reference card for efusA9 (https://www.fs-net.de/assets/d…PIO-ReferenceCard_eng.pdf) Furthermore if mxcfb0 is a first user of the IPU so it will get an overlay. It will create fb0 (main framebuffer) and fb1 (overlay). mxcfb1 is the second user of IPU so it get no overlay and create only fb2 (main framebuffer).

In your case the settings

must be correct. Framebuffer in this case are:
- rgb lcd fb0 mainframebuffer and fb1 overlay
- lvds has only mainframebuffer fb2

Hope that helps.

Hello,

you can use serial debug port. Please see chapter "4. Bringing Up the System" in first steps for more information. (https://www.fs-net.de/filelicence/get?fileid=165&locale=en_US)

Hello,

unfortunately we don't have software SPI driver (GPIO). The driver is initially planned for the kernel release 2.4. The planning, you can see in our roadmap for Vybrid boards.

Best Regards
Support Team

Hello,

maybe you can find some helpful informations in this post.
http://forum.fs-net.de/index.p…0&highlight=ssh#post12720

http://forum.fs-net.de/index.p…0&highlight=ssh#post12720Best regards
Support Teamhttp://forum.fs-net.de/index.p…0&highlight=ssh#post12720

http://forum.fs-net.de/index.p…0&highlight=ssh#post12720

Hello,

it looks like an bug in configuration file. Can you modify the configuration file "(linuxroot)/arch/arm/mach-mx6/Kconfig":

• remove exclamation mark from the line 958 (depends on !TOUCHSCREEN_ATMEL_MXT)
• enable atmel touch via menuconfig at System Type / Freescale MXC Implementations / Support F&S Eletronik Systeme GmbH PicoMODA9
• rebuild the image

Hope that helps.

Hello Marc,

with improved driver we handles followed flash memory problem.

When flash memory is read many many times, some bits may flip after a long period of time. These are called read disturbs. To avoid getting read errors from these toggled bits, the NAND flash must support a error correction via ECC. By default we are using an ECC that is capable of detecting and correcting up to 4 bit errors per 2K page. If a page shows many bitflips, the whole block is erased and re-written. This is a known procedure to revert bitflips caused by read disturbs.

Remember the strategy isn't safe if power fails during block refresh.

Quote

Further we also have problems, that our Executable, which is the Device Firmware, gets damaged from time to time. Will the improved ECC also improve the Data Integrity on the FFSDISK?

Yes, but only data integrity of written page (block). The driver don't handle atomic read/write file operations . This is a function of a file system. E.g. our file system F3S guaranteed atomic R/W operations.

Quote

Another question is, if the ECC detects an Error when loading the Kernel, if the Bootloader/Kernel will write the corrected version of the Kernel back to the Read-Only Kernel Storage area? Otherwise Errors can accumulate over time...

Yes, in this case a page (block) will be refreshed. Read only is a capabiliaty of a file system.

Hello,

that can be many reasions. One can be differt test enviroment.
I don't rule out possibility that a problem is in the driver or DLL, but currently i cann't reproduce the behaviour of your test enviroment. So i think it would more effiecent if you would give me more details. (source code of your application, exatly description of your test evniroment)

Hello,

can you send please a mail to supportATfs-net.de. My colleague will contact you.

Best regards

Hello,

my colleague has tested a display which is supported by PicoMOD6. He used a script with same parameters as yours. I dont compared the parameter exactly so it is possible that the values were a little different because it was other display. But it was same user mode.
We think that it would more efficient if you send us your display and we try to understand your problem here in our company.

Best regards

Hello,

Quote

-Do you configure CAN port with CANCheck tool in any special way for supporting both kind of frames in reception?

No, i used extended mode.

Quote

-Do you change this configuration for receiving i.e. EXT and then change again for receiving STD, or with an unique configuration flags you can receive both? (because changing configuration we are able to receive both too, but we need to receive both with a unique configuration of CAN port in order to distinguish which frame received is EXT and which one is STD).

You can receive both message formats if your receiver device configured in extended mode.

Quote

-CANCheck is not programmed with .NET and does not use F&S CAN wrapper dll, then the problem could be there...can you then try to use in a .Net project your CAN dll wrapper and try to see if with any combination of CAN flag configuration are you able to receive both kind of frames simultaneoulsy ??

I tested it with CAN wrapper dll and had same result. It works fine for me.

I think, it would be easier if you can send me your test application and describe your environment exatly (maybe with a diagram).
Probably i don't understand you test environment in details.

Hello,

i cann't reproduce described behaviour. I use CANCheck tool to receive extended and standard messages from 2 CAN devices and it works fine for me. Can you probaly do same test with CANCheck tool.

Hello,

you can find detailed information about CAN in our CAN driver documentation. (https://www.fs-net.de/assets/d…/WINCE_CAN_DOTNET_eng.pdf) In chapter "Sample Program Read" is a source code sample for receiving messages.

Hello,

for calibration we are using touch calibration dll from "fs_tchcaldll.dll" (registry entry [HLM\SYSTEM\GWE\TouchProxy]). This library has same functionality as the original library "tchcaldll.dll".
More details you can find on MSDN site:
- touch driver registry settings: http://msdn.microsoft.com/en-us/library/gg157868.aspx
- touch calibration functions: http://msdn.microsoft.com/en-us/library/gg158491.aspx

Hello,

i have tried to enable user display mode 101 and thats work fine for me. Can you enable debug output and check activated display mode?
It looks like that F&S Board Config has a bug.

Hello,

do you use lastest stable release? If yes, can you try a latest beta kernel XIPIMX6SDL_BETA_C7E_141028.zip from download area and give me a feedback.

Hello,

more information about display settings you can find in our documentation:
1) Timing interface
a) Display datasheet from manufacturer
b) https://www.fs-net.de/assets/d…ttings_from_datasheet.pdf
2) Some other helpful Information in device driver documentation. E.g. for FSVybrid Chapter 10 ( https://www.fs-net.de/assets/d…BRID_DeviceDriver_eng.pdf )
Device driver docu for PMA9 is comming soon.

Thanks.
This message means that by waiting for next read event timeout occurs, because no events are available. This message will removed by next driver release. New driver is available now.