Posts by Mike

  • Change Kernel form WinCE to Linux

    Thats good to know.


    Since we are currently using the PicoMod7A, I'd like to ask if the StarterKit board for PM7A is compatible with a newer PMA9 or if I'd need to get a newer board for any tests?


    Best regards

  • Change Kernel form WinCE to Linux

    Good day,


    would the PicoModA9 be able to support dotNet Core? Or would this need some work from the side of F&S?

    I am asking since we are currently discussing about switching to Linux as operationg system, in the next project.


    Best regards

  • Change Kernel form WinCE to Linux

    As I have written above:

    Quote

    the PicoMOD seems unable to access the USB and the SD-Card

    So currently I am not able to use either of the devices. Are there any other possibilities?


    I know that PicoMod7A is not recommended for new developments, I would only like to test some features before we start a development procedure.

    Like integration of DotNet Core for example.


    Best regards

  • Change Kernel form WinCE to Linux

    Good day,


    Currently, I am trying to replace the WinCE Kernel on one of our PicoMods with the Linux Kernel.


    I am following the First-Steps guide found in the download directory.

    After some trial and error i managed to replace the uboot, by using the serial download via DCU-Term.

    This was needed since the PicoMod seems to be unable to find the SD-card. "Can't access SD-card in FAT mode" is the only reply I am able to receive.


    The used SD-card is working if the device is running with the WinCE Kernel, even though I am not sure if its working during the boot procedures, since I didn't need to do these steps up until now.


    My current problem is that the PicoMOD seems unable to access the USB and the SD-Card, now that it should install the Kernel.

    This is the reply after system start with uboot:

    I would appreciate any help you are able to provide me.


    Best regards

  • VS2008 Debug Problem - SDK FSS5PV210 CE6

    Hello,


    I got it to work by following the advice in the link below:
    http://hehuvision.blogspot.co.…8-debugger-is-broken.html


    It seems that the already installed VS2015 collided with VS2008 in some way which got the Debugger .dll to act whacky.


    The fix for my problem was to register the debugger .dll manually by using the following CMDs:


    regsvr32 "C:\Program Files\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
    And for x64 Systems:

    regsvr32 "C:\Program Files(x86)\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"


    It seems like the fix posted in your link repairs the problem by removing and reinstalling the dll. Where the reinstall seems to force a registration Debugger.


    Anyways thanks for your help in solving this problem.


    Best regards

  • VS2008 Debug Problem - SDK FSS5PV210 CE6

    The error message is as follows:


    Das Programm XXX kann nicht gestartet werden
    Ein Fehler ist aufgetreten der meist auf eine Fehlerhafte Installation hinweist. Error code 0x80004002


    As far as I researched, this seems to be an error with the remote debugging tool of VS.
    Most people could fix it by installing the "Windows Remote debugging tool".
    I tried that, but it didn't lead to positive results.


    To me it seems like a similiar problem as in this thread:
    SDK für WEC7


    I do think to remember that I installted the file mentioned in the thread on my old PC, but it also didn't help.


    After reading the thread you posted, I went and compared the debugging options, under Tools->Options->Projects and Solutions->VC++ Directories, between my new and old PC, but couldn't really find any differences.


    Do you have any ideas i might be able to try?
    I'm more or less grapsing for straws over here.


    Thanks and best regards

  • VS2008 Debug Problem - SDK FSS5PV210 CE6

    Hello,


    I've got a problem with debugging my PicoMOD7A and NetDCU8 devices with VS2008 at my new PC.


    At my old PC it worked just fine, but I remember that the installation of the SDK can be a little bit tricky.
    For the new PC I installed
    VS08pro + SP1
    Ndcu8 SDK
    PicoMOD_WCE6 SDK


    in that order.


    The problem is, that every time I try to debug any Software(new and old; PM7A and NDCU8), I get an error that the debug failed and a repair of VS2008 is needed.
    Start of the software without debugging works, as well as all the Remote tools.


    Is there anything in the installation I might have missed?
    Thanks in andvance


    Best regards

  • Disable LCD Driver

    Now tested some Outputs of Port4 with Kernel V1.11:


    I now set the whole Port as Output and am switching the Port between High and Low.
    The following Currently only got Pin 63 and 66 to work as expected.
    Measurements on the following pins results in 0V: 61, 64, 67 and 70.


    I did the tests on another PicoMod too, with the same results.


    Further measurements und Port5 Pin 72, 74, 76, 78 work as expected.

  • Disable LCD Driver

    Debug during startup:


    Opening of the port and set outputs to false


    Set output to true and closing of the port:


    Thank you for the help

  • Disable LCD Driver

    Thank you for the help, it's working with limited success now.


    As written above we are using the PINs 61, 63 and 67 (all on Port4), but currently only PIN 63 seems to work properly now.
    I've meassured the voltage on the Pins and the PicoMOD seems unable to drive the PINs 61 and 67. (0V) I also used the PIN 65 as reverence, but also without success(registry was reconfigured for this purpose).


    The registry settings for the IOs is as follows:


    and the Display driver is set to ddi_nop.dll.
    Furthermore I've found the Display.dll revereced in HKLM\System\GDI\Drivers but setting it to ddi_nop doesn't seem to fix the problem.


    In the software I've tried setting the according bits for these pins (0,2,6) and also to set the entire Port4.


    Do you have any suggestions what I might be doing wrong?
    Best regards

  • Disable LCD Driver

    Hello.


    We are currently trying to use the Pins 61,63 and 67 as Outputs.
    Therefor we need to deaktivate the LCD display.


    To do this we need to set the DLL registry key in \Drivers\Display\LCD to DDI_NOP.dll. Correct?
    Currently this did not work in our trials. The moment we set the dll the PicoMod becomes unable to start.


    The DDI_NOP.dll should be in the windows Folder of the PicoMOD, but we couldn't find it.


    Were there any changes to deaktivate the LCD with the PicoMOD or can we download the DDL somewhere?


    Best regards

  • Internal PullUp DIO

    Good day!


    Are the internal pullups, of the picomod7A, usable for digital inputs.
    If yes, what value are they?


    Can they be used instead of external ones, properly?


    Best regards

  • Problem with multiple CS-Pins SPI

    The default pin is working now.


    We are going to test the application till next monday, and will post any results then.


    Edit:
    After running some tests with different IOs and a longtime test over the last week it seems like the driver is ok and can be released.


    Thank you for your fast help.

  • Problem with multiple CS-Pins SPI

    The read only is documented in the currently linked device driver file at the PicoMod7A (24.01.2013). See port description 4.1, Port2 Pin2;


    But can this driver still use the standard CsPin?
    We tested the multi CsPin usage with the default CsPin and the IO-Pin 18 and it seems like the default pin isn't driven.
    Both CsPins are driven correctly if we use 2 IO-Pins.

  • Problem with multiple CS-Pins SPI

    Thank you for your fast help!


    We used the new driver and it seems to work without any problems.


    One question though:
    We are able to use the IO-Pin 18 as CS and it works, but I read afterwards that this pin should be read only(specified in the device driver file).
    Is it possible that errors or any other errors occure if we keep on using this pin?

  • Problem with multiple CS-Pins SPI

    Hello!


    We tried using the new driver, but had only partial success.
    The default CsPin isn't used anymore, but we dont get a "High" signal on the defined pin either.
    The configured CsPin stays on a "Low" signal and doesn't budge. The software receives a timeout error message right after.


    We tried the following CsPin settings: 75, 126, 18, 45 all in dez;
    Which enumberation do we need to use for the configuration? Board Pins(126dez) or the IO-Pins(75)


    The Debug Output:

  • Problem with multiple CS-Pins SPI

    We are currently working on a device with 2 SPI controlled analog outputs.


    We configured one device to use the PicoMOD Pin 126(dez), which should be configured with the value 75(dez), as the CsPin.
    But it seems like the registry value is ignored by the system, and the default CsPin (Pin 1) is used instead.


    Our registry settings for reference:
    Device1:
    Prefix = SPI
    Index = 1
    DLL = nspi.dll
    Order = 101
    FriendlyName = Native SPI driver
    CsPin = 75


    Device2:
    Prefic = SPI
    Index = 2
    DLL = nspi.dll
    Order = 102
    FriendlyName = Native SPI driver


    Please note that we already removed device2 from the registry, for further testing on device1.


    The nspi driver version is 3.1
    The used class is NativeSPI.dll (V2.00) for c#.


    The initialisation of the SPI is done by the software:


    nspi = new NspiPort("SPI1:", NspiPort.NspiAccess.WRITE);
    nspi.ClockFreq = 250000;
    nspi.SpiMode = 0;
    nspi.Method = NspiPort.DriverMethod.POLLING;


    Could you tell us, if there is some error in the registry setting for the SPI device?
    Or are there only specific I/Os that can be used as CsPin?