Posts by Ralf

Hello,
now my colleague for hardware made some tests of our circuit. He cut the signal to the IC who regulate the power of the usb.
And we remove the settings for DIO-IO-Pin7 (USB-PWR) to factory settings. But never change the result of flickering usb-stick and no mounting
the device. OK, now we know the problem we have to search at our site.
First we compare it with your SKIT circuit and my colleague found some different places. For a better understanding I send you the part of our circuit who describes the usb control.
For this we have also a question:
In our circuit you can see the red and green encircled parts. If we remove the resistors, the usb works fine. But have we also remove the coils?

[IMG:http://www.leibinger-group.com/public/images/Schaltplanauszug3.JPG]

Any news for that problem? We are still waiting for a solution.

Next information:
We messaure the output pin of the driver IC for usb-power, but there is allways still at 5 Voltage. That should be correct.
If we connect the mouse without an usb-stick, everything is OK. Here the debug output:

UsbHost : New Function [address(1) / layer(0)]
Attach moutouchHID
USBHost : Detach Function [address(1) / layer (0)]
Detach moutouchHID
UsbHost : New Function [address(1) / layer(0)]
Attach moutouchHID
USBHost : Detach Function [address(1) / layer (0)]
Detach moutouchHID

But if we connect the usb-stick never hapens at the debug output and the stick is still blinking.

OK, sorry. The next trial:

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Jul 1 2013 15:25:38
Microsoft Windows CE Bootloader for PicoCOMA5 Built Jul 2 2013
Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
Boot Loader, Version 0.2
NBoot, Version VN04
HW rev. 1.0




System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
Kernel (47454kB) read from flash disk started finished in 6888 milliseconds
INFO: OEMLaunch: Jumping to Physical Address 0x80106740h (Virtual Address 0x0h)...







Jumping to Kernel @ 0x80106740
Windows CE Kernel for ARM (Thumb Enabled)
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
OAL Log enable : 1
OAL Log mask : 3
0x82f675c0
0x50
+OALTimerInit(1 131 0)
g_pGPC PA=0x4006c000 VA = 0xb006c000
g_pGPC->LPMR=0x0
g_pGPC->PGSR=0x0
g_pCCM->CLPCR=0x78
cmp=0x83




PicoCOMA5 V0.08 - Firmware Init
Copyright (c) 2013 F&S Elektronik Systeme GmbH
Build: Sep 10 2013/12:05:01
OAL: CPACR=0xf00000 NSACR=0xc00
========
CPU Info
========
CPU ID 0xc05
CPU Revision 0x0 0x1
Total CPUs 1
SMP is supported 1
THUMB is supported 4
JAZELLE is supported 1
VFP is supported 1
UTLB is supported 1
Maintenance broadcast 2
Pvt timer freq in MHz 66000000
=========
Plat Info
=========
Board is RTSM 0
L2 is extern 0
Periph Base 0x40002000
SCU Base 0x40002000
==========
Cache Info
==========
L1 I Sets 512
L1 I Ways 2
L1 I Line Sz 32
L1 I Sz 32768
L1 D Sets 256
L1 D Ways 4
L1 D Line Sz 32
L1 D Sz 32768
L2 Sets 0
L2 Ways 0
L2 Line Sz 0
L2 Sz 0
=========
Overrides
=========
====================
OALIoCtlHalInitRTC(2006/1/1 12:0:0.000)
WARNING: SNVS was reset.
cBoardConfig.chFeatures1=0x2 0 chBoardType=0x1
[OAL] MACB: Disabled
[OAL] RestartReason: Reset
FMD: g_pNFConReg=0xcc660000 --> FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
FMD: Block 0 to 16 are locked for boot loader
PM-NETDCU: STARTED
BE2: Version 1.3, ActiveKey = Drivers\Active\03
before ConfigOTGHOST:: regs->OTG_CTRL= 2001000
after ConfigOTGHOST:: regs->OTG_CTRL= 2021000
after ConfigOTGHOST:: regs->OTG_CTRL= 80000000
InitializeTransceiver: IRQ=108, sysIntr=17
NI2C: Version 0.5, ActiveKey = Drivers\Active\13
ENET: Version 01.00, ActiveKey = Comm\ETHNETA
BE2: Version 1.3, ActiveKey = Drivers\Active\15
NI2C: Version 0.5, ActiveKey = Drivers\Active\16
UART: Version 1.4, Key = Drivers\Active\17
UART: Port disabled. Serial debug is on !
UART: Version 1.4, Key = Drivers\Active\18
CID: Version 2.1, ActiveKey = Drivers\Active\19
AIN: Version 1.1, ActiveKey = Drivers\Active\21
PWM: Version 1.2, ActiveKey = Drivers\Active\22
I2C: Version 4.2, ActiveKey = Drivers\Active\23
WAV: Version 2.3, ActiveKey = Drivers\Active\24
TCH: Version 0.5, ActiveKey = Drivers\Active\25
SDHC: Version 1.0, ActiveKey = Drivers\Active\26
BCS: Version 1.3, ActiveKey = Drivers\Active\35
NSPI: Version 3.0, ActiveKey = Drivers\Active\36
DIO: Version 2.7, ActiveKey = Drivers\Active\37
DIO: UseAsIO[0] = 0x00000080
DIO: DataDir[0] = 0x00000080
DIO: DataInit[0] = 0x00000000
DIO: IRQCFG0[0] = 0x00000000
DIO: IRQCFG1[0] = 0x00000000
DIO: IRQCFG2[0] = 0x00000000
DIO: PullUp[0] = 0x00000000
DIO: PullDown[0] = 0x00000000
DIO: UseAsIO[1] = 0x00000000
DIO: DataDir[1] = 0x00000000
DIO: DataInit[1] = 0x00000000
DIO: IRQCFG0[1] = 0x00000000
DIO: IRQCFG1[1] = 0x00000000
DIO: IRQCFG2[1] = 0x00000000
DIO: PullUp[1] = 0x00000000
DIO: PullDown[1] = 0x00000000
DIO: UseAsIO[2] = 0x00000000
DIO: DataDir[2] = 0x00000000
DIO: DataInit[2] = 0x00000000
DIO: IRQCFG0[2] = 0x00000000
DIO: IRQCFG1[2] = 0x00000000
DIO: IRQCFG2[2] = 0x00000000
DIO: PullUp[2] = 0x00000000
DIO: PullDown[2] = 0x00000000
DIO: UseAsIO[3] = 0x00000000
DIO: DataDir[3] = 0x00000000
DIO: DataInit[3] = 0x00000000
DIO: IRQCFG0[3] = 0x00000000
DIO: IRQCFG1[3] = 0x00000000
DIO: IRQCFG2[3] = 0x00000000
DIO: PullUp[3] = 0x00000000
DIO: PullDown[3] = 0x00000000
DIO: ++InitPortMasks
DIO: #7 : Output
DIO: --InitPortMasks
DIO: --DIO_Init
DIO: +DIO_Open(0xcd3bb5d0)
DIO: DIO_Open(0xcd3bb5d0) returning -1002300304
DIO: +DIO_IOControl(): hOpenContext=0xC4421C70, dwIoControlCode=4, pBufIn=0xcc80f0d0, dwLenIn=8, pBufOut=0x0, dwLenOut=0, pdwActualOut=0xcc80ef04
DIO: +DIO_Close()
DIO: -DIO_Close done
LCD: Version 1.2, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: ASTADPEDT1.dll - Init failed
LCD: Could not intialize external PWM device AstADPEP1 (LE:2)
LCD: Display-Mode 100, Name Kyocera TCG121SVLx
[DISP]++Disp_envid_onoff(0)
[DISP]--Disp_envid_onoff() : 1
Disp_UpdateLCDC: DCU0 inclk=452571426, calc_freq=0, dwDiv is 11
Disp_UpdateLCDC: dcu_div is 11
[DISP]++Disp_envid_onoff(1)
[DISP]--Disp_envid_onoff() : 1
Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated. Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
NDCUCFG V 55 started. Platform: PicoCOMA
NDCUCFG Open COM1: at 38400 Baud
CreateFile() failed -> ERROR COM1:
CheckAutoStart: Version 1.6, LaunchNum = 100

Hello,

I forgot to say, if I connect a mouse to the usb host, there LED will still blinking. It looks like, that the usb power switch on and switch off all the time.

Following the debug output file:

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Jul 1 2013 15:25:38
Microsoft Windows CE Bootloader for PicoCOMA5 Built Jul 2 2013
Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
Boot Loader, Version 0.2
NBoot, Version VN04
HW rev. 1.0




System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
Kernel (47454kB) read from flash disk started finished in 6874 milliseconds
INFO: OEMLaunch: Jumping to Physical Address 0x80106740h (Virtual Address 0x0h)...







Jumping to Kernel @ 0x80106740
Windows CE Kernel for ARM (Thumb Enabled)
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
OAL Log enable : 1
OAL Log mask : 3
0x82f675c0
0x50
+OALTimerInit(1 131 0)
g_pGPC PA=0x4006c000 VA = 0xb006c000
g_pGPC->LPMR=0x0
g_pGPC->PGSR=0x8
g_pCCM->CLPCR=0x78
cmp=0x83




PicoCOMA5 V0.08 - Firmware Init
Copyright (c) 2013 F&S Elektronik Systeme GmbH
Build: Sep 10 2013/12:05:01
OAL: CPACR=0xf00000 NSACR=0xc00
========
CPU Info
========
CPU ID 0xc05
CPU Revision 0x0 0x1
Total CPUs 1
SMP is supported 1
THUMB is supported 4
JAZELLE is supported 1
VFP is supported 1
UTLB is supported 1
Maintenance broadcast 2
Pvt timer freq in MHz 66000000
=========
Plat Info
=========
Board is RTSM 0
L2 is extern 0
Periph Base 0x40002000
SCU Base 0x40002000
==========
Cache Info
==========
L1 I Sets 512
L1 I Ways 2
L1 I Line Sz 32
L1 I Sz 32768
L1 D Sets 256
L1 D Ways 4
L1 D Line Sz 32
L1 D Sz 32768
L2 Sets 0
L2 Ways 0
L2 Line Sz 0
L2 Sz 0
=========
Overrides
=========
====================
OALIoCtlHalInitRTC(2006/1/1 12:0:0.000)
cBoardConfig.chFeatures1=0x2 0 chBoardType=0x1
[OAL] MACB: Disabled
[OAL] RestartReason: <UNKNOWN>
FMD: g_pNFConReg=0xcc660000 --> FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
FMD: Block 0 to 331 are locked for boot loader
PM-NETDCU: STARTED
BE2: Version 1.3, ActiveKey = Drivers\Active\03
before ConfigOTGHOST:: regs->OTG_CTRL= 2001000
after ConfigOTGHOST:: regs->OTG_CTRL= 2021000
after ConfigOTGHOST:: regs->OTG_CTRL= 80000000
InitializeTransceiver: IRQ=108, sysIntr=17
NI2C: Version 0.5, ActiveKey = Drivers\Active\13
ENET: Version 01.00, ActiveKey = Comm\ETHNETA
BE2: Version 1.3, ActiveKey = Drivers\Active\15
NI2C: Version 0.5, ActiveKey = Drivers\Active\16
UART: Version 1.4, Key = Drivers\Active\17
UART: Port disabled. Serial debug is on !
UART: Version 1.4, Key = Drivers\Active\18
CID: Version 2.1, ActiveKey = Drivers\Active\19
AIN: Version 1.1, ActiveKey = Drivers\Active\21
PWM: Version 1.2, ActiveKey = Drivers\Active\22
I2C: Version 4.2, ActiveKey = Drivers\Active\23
WAV: Version 2.3, ActiveKey = Drivers\Active\24
TCH: Version 0.5, ActiveKey = Drivers\Active\25
SDHC: Version 1.0, ActiveKey = Drivers\Active\26
BCS: Version 1.3, ActiveKey = Drivers\Active\35
NSPI: Version 3.0, ActiveKey = Drivers\Active\36
DIO: Version 2.7, ActiveKey = Drivers\Active\37
LCD: Version 1.2, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: ASTADPEDT1.dll - Init failed
LCD: Could not intialize external PWM device AstADPEP1 (LE:2)
LCD: Display-Mode 100, Name AUO G104SN03
[DISP]++Disp_envid_onoff(0)
[DISP]--Disp_envid_onoff() : 1
Disp_UpdateLCDC: DCU0 inclk=452571426, calc_freq=0, dwDiv is 11
Disp_UpdateLCDC: dcu_div is 11
[DISP]++Disp_envid_onoff(1)
[DISP]--Disp_envid_onoff() : 1
CheckAutoStart: Version 1.6, LaunchNum = 100
Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated. Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
Warning: you are requesting IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated. Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.

Hello,

you are right. Sorry, I have to explain the whole story for this problem:
At our Hardware, we have an IC to switch the power for the usb that is low active. Until now, with PicoCOM4 we solved this problem to set the DIO-IO-Pin usb-power as an UseAsIO = 1 , DataDir = 1 and DataInit = 0. With this settings it works fine. Now the same settings at PicoCOMA5 do not work. Now my question:
Is there a posibility to set this at the usb-driver or if not, what should we do?

Kernel: NKVYB_CZE_130910.bin
I checked several USB-Sticks, but everytime the same result. The usb-stick access-LED is still blinking, but no folder is displaying at the file explorer. I don't use a usb-hub! The stick is directly connected.

Hello,

thanks for the fast work. The input adjustments of Port2 works correctly now.
But I have a new problem!
The new driver will not dedect an USB device --> e.g. ActiveSync connection.
The same problem I have with PicoCOM3 Kernel Version V1.01 with evaluation board. Can you also check it?

Hello,

we also have the same problems. But in our case we have made an own kernel and many boards with that wrong DIO driver are sold.
Now my questions: Is it possible to exchange the driver in the current kernel, without installing a new kernel?
And is it possible to get this DIO driver as soon as possible, because our customers need that input pin very urgent.

Hello,

Does someone have experience with MUI kernel? Short explanation: I need a kernel that can switch between the normal system font “Tahoma†and three additional Asian fonts like “SimSun†for Chinese, “MingLiU†for Taiwan and “Gulim†for Korea. I had already successfully reached this under Windows CE 5.0. However under Windows 6.0 it does not work. In detail: The Asian fonts needs very much memory and we do not have more than 64 MByte RAM. For that reason, we would like to include two of that three Asian fonts during run-time. And here is the problem. If we include the fonts at run time with the function “AddFontRescource†no Asian characters will be displayed. For testing all MUI parameters, I have made a kernel that includes all three Asian fonts (Kernel image 33 MByte). In that case all Asian characters will be displayed. May be someone have an idea about a hidden switch, which I overlooked?

Hello,

sorry, I was probably too rash. Because, when I use your kernel image, everything is OK.
That means you do not have to look longer for this error.

In my own kernel, I do not have included the ndcucfg catalog item. So I copied the ndcucfg program
in the FFSDISK folder and start it. The most commands are working fine, only the "serial debug off", will not work.
Now, I will make a new image with including ndcucfg. I hope that was the reason.

Hello,

thanks for your answers. But I don't have problems to save any registry paramerters.
I also find the thread: HOWTO: execute NDCUCFG command
By the way, I use to get and set registry settings with the registry class. For example to save the ip-adress:

After that, you have to restart the PicoCOM.
My problem is, if I start the ndcucfg editor and type in the command "serial debug off" it will display an "OK", but it has no function.
Only when I type dirctley in the DCUTermi an "O" and afterwards a "Y" it will work!

Hello,

the whole day I study the forum about "Debug output at COM1" and I found a lot of articles, but none of them could helped me.
I want to switch off the serial debug at COM1! OK. I can do this in the eboot with the command "O". This works fine.
But I want to control it automatically from my program. So I try it to start your program ndcucfg.exe and send it the command
"serial debug off" with following command "reboot". The "reboot" command works fine, but the "serial debug off" has no function.
What can I do?
The best would be, the "serial debug" parameter is from beginning off. Or can I do some settings in the registry to switch off the serial debug?

Hello,

here are my measurement arguments from the spi communication between PicoCOM2 and PicoCOM4.
In the first picture you can see the clock (yellow) and the MOSI signal from PicoCOM2 during a “DeviceIOControl†command.
In the second picture are the same from PicoCOM4. We used the same software at both boards.
You wrote you have tested the nspi driver and you made hardware modifications. For this reason we ordered new PicoCOM4
from our distributor. But we have still the communication problems. Please, we need answer as soon as possible.

[IMG:http://img4web.s3.amazonaws.com/source/GSHDUC.jpg?AWSAccessKeyId=1SC7XPM4CHJWESHW9XG2&Expires=1317637029&Signature=0c3Cqic1fZojAD7ZEJD3ArVrGxE%3D]

[IMG:http://img4web.s3.amazonaws.com/source/5NYXJ.jpg?AWSAccessKeyId=1SC7XPM4CHJWESHW9XG2&Expires=1317636962&Signature=AJYCtKVi8%2FY%2BikIk9FVUqUXPuik%3D]

Hello,

because of your last answer we ordered two new PicoCOM4 from our distributor. But we have still the same problem!
What is now the newest HW revision. On the board I can read "PicoCOM4 R:1.11".
It is very important for us to know, that our software working likewise on PicoCOM2.
Because we want to order and it is very urgently.

Hello,

one more question:
Did you tested the nspi driver on PicoCOM4?

Hello,

unfortunately we have still problems with the SPI driver. CAN Bus driver is not installed!
We don't meassure any clock signal at the clock pin. Maybe you can see any mistakes in the output log file .

Now it is very important for us to know the PicoCOM4 SPI is working well.
Because we have to order a lot of PicoCOM4 as soon as possible.

Hello,

I have a question about SPI:
We start our development with PicoCOM2 and want to change to PicoCOM4. With PicoCOM2 we have a successfull communication with the SPI-bus. Now I thougt we can use nearly the same registry parameters from PicoCOM2 SPI to PicoCOM4 SPI. But the commuication is fail. I tried different settings but without success.
Until now, we can find a description of PicoCOM_NSPI_eng.pdf on your server, but this PDF document descripe only PicoCOM1 and PicoCOM2. Is there any different to PicoCOM4?
Maybe you can help me, what parameter settings are wrong?
First the part of registry settings SPI PicoCOM2:

And here are the current SPI settings of PicoCOM4:

Hello,

thanks for this info about the template. Now it works.