So I think I need to ask you, would it be possible for you to build it for ARM platform and preferably make it console application?
Thanks!
Posts by farhadd
-
-
I think I found a solution:
https://developer.microsoft.co…s/externalprocesslauncherBut the thing is I'm trying to setup a Raspberry pi and NetDCUUSBLoader is not built for ARM processor.
-
Hi,
I am trying to desing a new app on windows 10 for downloading the Windows CE kernel to the board in productopn. In the past I used to run NetDCUUSBLoader.exe as an external process in my software. But in UWP(Universal winodws platfrom) it's no longer possible to launch executables.
I was wondering if there is any workaround?
Can we have access to the source code of NetDCUUSBLoader? in this manner it would be possible to re-use the code internally in other applications..Cheers,
Farhad -
Ok found it now!
-
Do you mean windows kernel image by "Latest System SW"?
if yes, the kernel version of my board is V1.03-Build Dec 4 2013.unfortunately I don't know how to access the download area. your website has changed a lot...
there are some other problems with dynamic method, I'll try to report them in the next post.
Thanks,
Farhad -
I chose the permanent method and did as you said but the display is not totally rotated yet.
I've also noticed the following errors in debug output after I set rotate parameter to 90:
Display MoreCode- Exception 'Data Abort' (4): Thread-Id=05fa0002(pth=88d96a38), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=05060002(pprc=88cc8328) 'explorer.exe'
- PC=c0155e28(gwes.dll+0x00015e28) RA=c0152ca8(gwes.dll+0x00012ca8) SP=d420f968, BVA=00000000
- Exception 'Raised Exception' (-1): Thread-Id=05fa0002(pth=88d96a38), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=05060002(pprc=88cc8328) 'explorer.exe'
- PC=c003bce8(k.coredll.dll+0x0001bce8) RA=801232c8(kernel.dll+0x000062c8) SP=d420f304, BVA=ffffffff
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b74c48b(???+0x3b74c48b) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=c48bc48b(???+0xc48bc48b) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b74c48b(???+0x3b74c48b) SP=d446f118, BVA=d337fc44
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=c48b3b74(???+0xc48b3b74) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b743b74(???+0x3b743b74) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b743b74(???+0x3b743b74) SP=d446f118, BVA=d337fc44
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b740000(???+0x3b740000) SP=d446f1bc, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af79e8(display.dll+0x000179e8) RA=c0af79e4(display.dll+0x000179e4) SP=d446ec7c, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af79e8(display.dll+0x000179e8) RA=c0af79e4(display.dll+0x000179e4) SP=d446f138, BVA=d337fd0e
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af79e8(display.dll+0x000179e8) RA=c0af79e4(display.dll+0x000179e4) SP=d446f138, BVA=d337fcd6
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0afe0cc(display.dll+0x0001e0cc) RA=c0ae4d24(display.dll+0x00004d24) SP=d446f10c, BVA=c71a5218
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0afe0cc(display.dll+0x0001e0cc) RA=c0ae4d24(display.dll+0x00004d24) SP=d446f158, BVA=c71a5218
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0afe0cc(display.dll+0x0001e0cc) RA=c0ae4d24(display.dll+0x00004d24) SP=d446f158, BVA=c71a5218
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af79e8(display.dll+0x000179e8) RA=c0af79e4(display.dll+0x000179e4) SP=d446ed1c, BVA=d337fd0e
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af14cc(display.dll+0x000114cc) RA=00000000(???+0x00000000) SP=d446ece4, BVA=c0adcb60
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b74dbc0(???+0x3b74dbc0) SP=d446f118, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=c48bdbc0(???+0xc48bdbc0) SP=d446f118, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b74c48b(???+0x3b74c48b) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=c48b243f(???+0xc48b243f) SP=d446f118, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b74243f(???+0x3b74243f) SP=d446f118, BVA=d337fc3c
- Exception 'Data Abort' (4): Thread-Id=060f0002(pth=88f450c0), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=060e0002(pprc=88f42da4) 'rnaapp.exe'
- PC=c0af1d40(display.dll+0x00011d40) RA=3b743b74(???+0x3b743b74) SP=d446f118, BVA=d337fc40
- Exception 'Data Abort' (4): Thread-Id=06380006(pth=88fd4d08), Proc-Id=00400002(pprc=8238a308) 'NK.EXE', VM-active=06370006(pprc=89015dc8) 'cerdisp2.exe'
- PC=c0af14cc(display.dll+0x000114cc) RA=00000000(???+0x00000000) SP=d462ec8c, BVA=c0adcb60
Could you help me to overcome this problem?
Thanks,
Farhad -
Where can I find the latest Window CE kernel for PicoComA5?
can you tell me how can I access the download area? -
Hi,
I'm trying to rotate the screen on PicoCOM A5. My display is "EDT ET057090"(mode 13).
So far I have swapped the values for height and width as well as "LPP","rows" with "PPL","columns" in registry settings.Please have a look to the screenshot of current look of my display. it seems that the desktop is not rotated at all however the task bar is in a proper place.
Is there anything I'm missing?Thanks in advance,
-
Hi,
I've been experimenting PicoComA5 since a while ago. it used to work fine but after a sudden I could never approach to windows screen. following is the debug output:Display MoreCode- 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 VN05
- HW rev. 1.10
- System ready!
- Preparing for download...
- Press >S< to step into monitor...
- AUTO BOOT enabled
- Kernel (49183kB) read from flash disk started finished in 6840 milliseconds
- INFO: OEMLaunch: Jumping to Physical Address 0x80108F80h (Virtual Address 0x0h)...
- Jumping to Kernel @ 0x80108F80
- Windows CE Kernel for ARM (Thumb Enabled)
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- OAL Log enable : 1
- OAL Log mask : 3
- 0x83147880
- 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 V1.01 - Firmware Init
- Copyright (c) 2013 F&S Elektronik Systeme GmbH
- Build: Nov 15 2013/16:31:54
- FMD: g_pNFConReg=0xb00e0000 --> FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
- FMD: Block 0 to 12 are locked for boot loader
- OAL: CPACR=0xf00000 NSACR=0x0
- ========
- 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=0x1 0 chBoardType=0x1
- [OAL] MACB: Disabled
- [OAL] RestartReason: <UNKNOWN>
- FMD: g_pNFConReg=0xcc660000 --> FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
- FMD: Block 0 to 12 are locked for boot loader
- PM-NETDCU: STARTED
Do you have any idea what can be the problem?
I think problem has raised when since changed the start up program from explorer.exe to my own software in the registry,however I tried "R" command in the bootloader menu several times after that but no success so yet! -
I'm just wondering when are you planing to release the first generation of PicoCOMA5 boards?
-
Do you have any suggestion of how to use a MATLAB code in WinCE? is it possible to generate DLL files under some certain circumstances and load it in windows CE projects?
Thanks,
Farhad -
I've realized that I wrote we're planning to use V1.12 but the debug info is for V1.11. I should mention that same is happening in V1.12.
-
It doesn't start at all, I'm not sure if it hangs or there is a hardware problem. following is the complete debug information when it crash:
Display MoreCode- Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Feb 16 2012 15:13:12
- Microsoft Windows CE Bootloader for PicoCOM4 Built Feb 16 2012
- Portions copyright (c) 2009 F&S Elektronik Systeme GmbH
- Boot Loader, Version 1.6
- NBoot, Version C426
- HW-Watchdog: ON
- System ready!
- Preparing for download...
- Press >S< to step into monitor...
- AUTO BOOT enabled
- Kernel (2547kB) read from flash disk started finished in 1 milliseconds
- INFO: OEMLaunch: Jumping to Physical Address 0x301422CCh (Virtual Address 0x0h)...
- Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 14 2011 at 17:32:03
- PicoCOM4 V1.11 - Firmware Init
- Copyright (c) 2010 F&S Elektronik Systeme GmbH
- Build: Oct 29 2012/12:44:30
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- HW-WATCHDOG: ENABLED
- FMD: NAND ID:0x2076 --> ST: 512MBit (64MB)
- FMD: IsBlockBad - Page #: 0x0
- FMD: IsBlockBad - Page #: 0x20
- FMD: Block 0 to 20 are locked for boot loader
- -OEMInit
- OALIoCtlHalInitRTC: Year: 2006, Month: 1, Day: 1, Hour: 12, Minute: 0, second: 0
- Time returned from OEMGetRealTime: Year: 2006, Month: 1, Day: 1, Hour: 12, Minute: 4, second: 26
- Drivers\Builtin\Serial1 - OFF
- RestartReason: Reset
- FMD: NAND ID:0x2076 --> ST: 512MBit (64MB)
- FMD: IsBlockBad - Page #: 0x0
- FMD: IsBlockBad - Page #: 0x20
- FMD: Block 0 to 20 are locked for boot loader
- FMD: FMD_OEMIoControl: unrecognized IOCTL (0x71c24).
- FSPART: FS partition driver loaded
- OEM: Not cleaning system hive
- OEM: Not cleaning user profiles
- OEM: Not cleaning system hive
- DIO-Layout: >=V1.20
- PM-NETDCU: STARTED
- +OALIoCtlHalGetHWEntropy
- OHCI: Version 1.2, ActiveKey = Drivers\BuiltIn\OHCI
- I2C: Version 2.5, ActiveKey = Drivers\Active\10
- PSS: Version 1.1, ActiveKey = Drivers\Active\11
- VDE: Version 1.0, ActiveKey = Drivers\Active\12
- NDIS:Version 1.0
- WAV: Version 1.0, ActiveKey = Drivers\Active\17
- CID: Version 2.8, ActiveKey = Drivers\Active\18
Thanks for your help
-
We're planning to migrate from V1.06 to V1.12. Sometime in the latest kernel when the board is powered up, WinCE doesn't boot up. Do you know what could be the problem?
I have to say, it used to work properly in V1.06.Cheers
-
Quote from "feder"
If starting PicCOM4 with pluged in USB-Stick, then the SD-Card is fail.I have same problem with kernel version 1.06. is there any solution?
-
Windows CE kernel "V1.06, 120119" cannot detect SD card if a high density USB memory stick(8GB) is inserted before boot up.
Do you have any suggestion about how can I resolve this issue?
-
Is there any way (Registry key) that I could retrieve the Kernel version?
-
Seems there is a bug in the latest kernel . I have set the "CardAvailable" key in [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\HSMMC] to 1,but there is no sign of SD card anywhere. Do you have any suggestion to solve this problem?
-
I've noticed that sometimes when a point is touched in (windows or my application) touch driver get a totally wrong place!
I have to say, same application works fine in PicoCom2.As an example I have a folder under "FFSDISK" directory which contains several files. when I try to point them on by one sometimes it make another file blue and behave randomly.
Do you have any idea?
-
I would like to know the Current specification on PicoCom2 and PicoCom4. I couldn't find any information on manuals.
would you please help me by providing those information?
