Posts by Andy.M

Hello,

I didn't find your version on my page : WinCE7 - Kernel V2.02 (XIPVYB_C7E_V2.0_150519.bin).

[IMG:http://i58.tinypic.com/20pwmpt.jpg]

But, I took something else : XIPVYB_C7E_V2.2_150513.bin.

I also fixed my registry entries, like that :

reg open \Comm\ftpd
reg set value LogFileDirectory string \FFSDISK\www
reg set value IsEnabled DWORD 1
reg set value UseAuthentication DWORD 0
reg set value AllowAnonymous DWORD 1
reg set value AllowAnonymousUpload DWORD 1
reg set value AllowAnonymousVroots DWORD 1
reg set value DefaultDir string "\FFSDISK"
reg set value IdleTimeout DWORD 300
reg set value DebugOutputChannels DWORD 2
reg set value DebugOutputMask DWORD 23
reg set value BaseDir string \
reg set value LogSize DWORD 4096
reg set value LogEnabled DWORD 1
reg open \Drivers\BuiltIn\DIGITALIO
reg del value UseAsIO
reg del value DataDir
reg del value DataInit
reg set value UseAsIoA DWORD 0x00000FFF
reg set value DataDirA DWORD 0x000000FF
reg set value DataInitA DWORD 0x00000000
reg save

It now works as expected.

Thank you very much.

Hi all,

I'm having troubles with the FTP on my NetDCUA5.

Here is my configuration :
(E)Boot Loader, Version 1.3 (EBOOTVYB_13.nb0)
NBoot, Version VN12 (nbootvyb_12.bin)
WinCE7 - Kernel V2.01 (XIPVYB_C7E_V2.0_150129.bin)

The FTP should be up and running by default but I can't connect (anonymously) on it.

Here are the only lines that are altered in my registry :

reg open \Ident
reg set value Name string CLA_BM_9999_99
reg open \Comm\ftpd
reg set value LogFileDirectory string \FFSDISK\www
reg open \Comm
reg set value IsEnabled DWORD 1
reg set value UseAuthentication DWORD 0
reg set value AllowAnonymous DWORD 1
reg set value AllowAnonymousUpload DWORD 1
reg set value AllowAnonymousVroots DWORD 1
reg set value DefaultDir string "\FFSDISK"
reg set value IdleTimeout DWORD 300
reg set value DebugOutputChannels DWORD 2
reg set value DebugOutputMask DWORD 23
reg set value BaseDir string \
reg set value LogSize DWORD 4096
reg set value LogEnabled DWORD 1
reg open \Drivers\BuiltIn\DIGITALIO
reg del value UseAsIO
reg del value DataDir
reg del value DataInit
reg set value UseAsIoA DWORD 0x00000FFF
reg set value DataDirA DWORD 0x000000FF
reg set value DataInitA DWORD 0x00000000
reg save

What am I missing here ?

My attempt :

1) Using the command line :
>> ftp CLA_BM_9999_99
<< Connected to CLA_BM_9999_99

Then I get a Timeout

2) Using Filezilla :
>> Connection established, waiting for greeting message

Timeout

3) Using windows Explorer :
Timeout

Okay, so everything is allright. Thank you for your answer.

I tried again with DCUTerm and after many attempts, one of them succeeded. I was able to chose 'd' under the following menu :

Please select action
'd' -> Serial download of bootloader
'E' -> Erase flash
'B' -> Show bad blocks
Use NetDCUUsbLoader for USB download

I selected my EBoot, It performed well.

I rebooted my card and It asked for my Mac Address... I followed your documentation and entered 000551 + my barcode and it went well. I chose DE to use EShell, selected my NetDCU card, chose my WinCE7 image, the installation went further away than the last one... I'm stuck here now :

Windows CE ethernet MAC address not set.
Enter WindowsCE MAC address (actual ff:ff:ff:ff:ff:ff): 0000005555110088FFAA110
0

MAC address for WindowsCE set to 00:05:51:08:fa:10

NetDCUA5 - WindowsCE Bootloader

:>
:> de
INFO: *** Device Name 'NetDCUA517927' ***
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 192.168.1.131

ProcessDHCP()::DHCP IP Address Resolved as 192.168.1.131, netmask: 255.255.255.0

Lease time: 604800 seconds
Got Response from DHCP server, IP address: 192.168.1.131
No ARP response in 2 seconds, assuming ownership of 192.168.1.131
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Packet has the following data:
boot.bin[NULL]octet[NULL]
TFTP packet could have 1 name/value pairs
Locked Down Link 1
Src IP 192.168.1.131 Port 03D4 Dest IP 192.168.1.105 Port E5D2
Default TFTP block size set to: 512 bytes
There were no options detected in the TFTP
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp

Download file information:
-------------------------------------------------------------------------------
[0]: Address=0x80100000 Length=0x38163BC Name=
BIN detected. Check MinImageStart ()
INFO: Changed start address for to 0x80100000.
-------------------------------------------------------------------------------
################################################################################
################################################################################
################################################################################
#########################################################1 files tranfered
Create partition for boot section ...
Success
Create partition for kernel section ...
FindFreeSector: FreeSector is: 0x243 after processing part 0x20.
Success
Create partition for FFSDISK section ...
FindFreeSector: FreeSector is: 0x243 after processing part 0x20.
FindFreeSector: FreeSector is: 0x8281 after processing part 0x21.
CreatePartition: Num sectors set to 0x7900 to allow for compaction blocks.
Success
WriteRegionsToNandFlash
INFO: [0] Found chain information (pChainInfo=0x8033B818 Extensions=0x3).
[Dump XIP Chain Summary]
- pvAddr: 0x80500000
- dwMaxLength : 16384
- usOrder : 0x0
- usFlags : 0x0
- reserved : 0x0
Writing single region/multi-region update, dwBINFSPartLength: 58811324
INFO: BP_OpenPartition: dwBINFSPartLength =0x38163BC).
dwRegionStart=0x80100000).
dwRegionLength=0x38163BC).
INFO: BP_SetDataPointer: Set data pointer in BINFS partition (offset=0x0).
INFO: WriteRegionsToNandFlash: Write region to BINFS partition (start=0x80100000
, length=0x38163BC).
Writing image to flash complete.
AUTO-BOOT enabled
All files flashed
OEMReadData: 0x4A
Leaving DownloadImage()
dwImageStart=0x80100000, dwImageLength=0x38163bc, dwLaunchAddr=0x8010a020
OEMAfterDownload(dwAction=0x0)
ROMHDR at Address 80100044h
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x0000000F
INFO: OEMLaunch: Jumping to Physical Address 0x8010A020h (Virtual Address 0x8010
A020h)...

Jumping to Kernel @ 0x8010A020
Windows CE Kernel for ARM (Thumb Enabled)
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

NetDCUA5 V1.09 - Firmware Init
Copyright (c) 2013 F&S Elektronik Systeme GmbH
Build: Sep 15 2014/15:48:50
FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
FMD: Block 0 to 14 are locked for boot loader
OAL: Enable SCU
WARNING: SNVS was reset.
I2C: Version 2.5
ERROR: OEMSetRealTime: NKSystemTimeToFileTime failed.
OAL: RestartReason=Power On Reset
FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
FMD: Block 0 to 14 are locked for boot loader
FSPART: FS partition driver loaded
BINFS: RegisterVolume - Mounted volume '\BINFS'
PM-NETDCU: STARTED
BE2: Version 1.4, ActiveKey = Drivers\Active\03
NI2C: Version 0.9, ActiveKey = Drivers\Active\15
BE2: Version 1.4, ActiveKey = Drivers\Active\16
UART: Version 1.13, Key = Drivers\Active\17
UART: Version 1.13, Key = Drivers\Active\19
UART: Port disabled. Serial debug is on !
UART: Version 1.13, Key = Drivers\Active\20
UART3 RS232 Configured
CID: Version 2.4, ActiveKey = Drivers\Active\21
CID: Version 2.4, ActiveKey = Drivers\Active\22
ENET: Version 01.03, ActiveKey = Comm\ETHNETA
PIF: Version 1.2, ActiveKey = Drivers\Active\24
Priority256 = 0x00000000 = 0 (Default)
WaitStates = 0x220f2220 = 571417120 (Default)
IRQPin = 0x00000068 = 104
IRQCfg = 0x00000002 = 2
IOBaseAddr = 0x30000000 = 805306368
PIF: freq=166736838Hz
PIF: freq=55578946Hz
PUI: Version 1.0, Key = Drivers\Active\25
ERROR: c:\wince700\platform\fsvybrid\src\drivers\uartintf\dll\uartintf.c line 10
07: UARTINTF not found or damaged. Can't init port.
PUI: Version 1.0, Key = Drivers\Active\26
ERROR: c:\wince700\platform\fsvybrid\src\drivers\uartintf\dll\uartintf.c line 10
07: UARTINTF not found or damaged. Can't init port.
AIN: Version 1.2, ActiveKey = Drivers\Active\27
PWM: Version 1.2, ActiveKey = Drivers\Active\28
EXTRTC: Version 1.1, ActiveKey = Drivers\Active\29
I2C: Version 4.2, ActiveKey = Drivers\Active\30
TCH: Version 0.6, ActiveKey = Drivers\Active\31
SDHC: Version 1.2, ActiveKey = Drivers\Active\32
WAV: Version 2.3, ActiveKey = Drivers\Active\34
ENET: Version 01.03, ActiveKey = Comm\ETHNETB
BCS: Version 1.4, ActiveKey = Drivers\Active\44
NSPI: Version 3.0, ActiveKey = Drivers\Active\45
DIO: Version 2.8, ActiveKey = Drivers\Active\46
FRW: Version 1.1, ActiveKey = Drivers\Active\52
LCD: Version 1.6, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Display-Mode 0, Name VGA standard display
NDCUCFG V 56 started. Platform: NetDCUA5
NDCUCFG Open COM1: at 38400 Baud
CreateFile() failed -> ERROCheckAutoStart: Version 1.7, LaunchNum = 100
R COM1:

Any idea what I did wrong ?

Edit : The card looks installed (I can TELNET it, I can go into the registry, I can connect on it with FTP) but this error with COM1 is very strange... I don't remember having this kind of message after updating my other NetDCUA5. Is there something strange here or not ? Since our application uses COM ports, I'll need to make sure my installation is correct... Is there a tool I can use to check that ?

Hi,

Thank you for your answer. I'm on a laptop and using the docking station to have a proper serial port plug.

I actually get error while trying to write on the serial communication.

I'll give Tera Term a try...

Thank you for your answer. The card I'm trying to switch the OS was a WCE 2013 before. Maybe that will help you understand the situation here.

Anyway, during the boot, I've pressed 's' and here is the result :

F&S Nand Loader VN05 built Sep 12 2013 12:14:43
NetDCUA5 Rev. 1.10
256MB RAM (1 chip) 128MB FLASH 500MHz 512kB L2
booted primary image from page 4

I've pressed 'B' for bad blocks and it tells me 'none'.

Is it up-to-date ? For practice purpose, I tried to follow the following document : https://www.fs-net.de/assets/download/bin/FSVYBRID/WinCE/FSVYBRID WInCE Update instructions.pdf

I've downloaded your DCUTerm but, even tho I've configured it like yours, I'm getting error when powering On the card and pressing s. Looks like I can't communicate with the card with DCUTerm. Alternatively, I'm using HyperTerminal without troubles.

Of course, using HyperTerminal does not allow me to send a new NBoot file. Is the trouble I'm having related to the version of Windows I have ? Is there a special version of DCUTerm for Windows 7 64 Bits ?

Hi all,

I'm trying to update a NetDCUA5 in order to change the OS that is installed on it.

I'm trying to download the WinCE 7 using the file XIPVYB_C7E_140915.bin. Everything works as expected except for the last part when the update process tries to jump to the kernel... The same happens when I try and install another image, such as a WinCE 2013 one.

[IMG:http://oi57.tinypic.com/osxqx2.jpg]

My update hangs there and I can't do anything else. I've been waiting for more than 15 minutes without much success... Is there a problem with my EBoot or NBoot or something related to this ?

We have some developments using Microsoft Embedded Visual C++ 4.00. They actually run on the NetDCU8 under WinCE 5.0.

I was wondering if it would be possible to have WinCE 5.0 on a NetDCUA5 card ? I hardly think it's possible due to hardware differences but, have you ever tried it ?

Do I risk something trying ?

All right, thank you for the answer.

Hi all,

I'm receiving the following error while trying to update the image of my NetDCUA5 card :

[IMG:http://oi58.tinypic.com/2817e5t.jpg]

The image I tried to restore has been found on My FS, it was the file : XIPVYB_C7P_140414.bin

What is the difference between :

• XIPVYB_C7E_140414.bin
• XIPVYB_C7P_140414.bin

I tried the E version afterwards and it seems to work...

All right,
a) It should be the latest, it's a card that came back from you last week.
b) I'm indeed working with disabled debug port
c) I stopped using those adapters, I had too much troubles with random devices. Now I'm only passing through a DELL Docking station. I've faced the problem while being connected directly on the COM port on another machine.

I'll give it a try with an enabled debug port and check the version of my N and EBoot, just to be sure. Thank you

Ok, after many attempts, I guess I finally succeeded. (in your last message, it should state "DE" instead of "DU" I guess)

Here are the screenshots of my final attempt :

[IMG:http://oi57.tinypic.com/2qmhv7o.jpg]

[IMG:http://oi58.tinypic.com/dcfn8m.jpg]

[IMG:http://oi57.tinypic.com/wvpr2g.jpg]

When connecting in Telnet, I receive now a Pocket Cmd 8.0. It seems to have work, do you see something wrong in the steps I followed ?

[IMG:http://oi61.tinypic.com/5xl8i1.jpg]

It's indeed not difficult when you know how to do... That being said, I faced lots of problem while having to hit "SHIFT+S". 19 times out of 20, it just wouldn't work, I couldn't enter EBoot configuration. When I try to enter NBoot configuration, pressing "s", it works 100% of the time. I don't understand why it does not work properly when pressing "SHIFT + S". I suspect my docking station or something around my usb keyboard... I've already faced that problem with other cards, with different ways to connect to them...

I guess it has to be my computer, but I don't know what it could be... Any idea ?

Note : Using CerDisp and CerHost, I remotely connected myself and checked... I'm indeed into WinCE 2013. That seems to have worked properly. If you have an idea on the trouble I'm facing (described right above), let me know how I could correct this...
Thank you for your help.

Then, the card was wrong from the start, because we especially ordered two cards, one with WinCE 6.0 and the other with WinCE 7.0. Since the first one is working with WinCE 6.0, if you tell me you never changed the OS, then you never sent us a card with WinCE 7.0. My end-customer result is, I don't have a card with WinCE 7.0 when I shoud have.

Anyway, I'm progressing, I switched the following entry within the registry :
\: HKEY_LOCAL_MACHINE\System\NDCUCFG
00 "Port"=string:COM1: \

I had to change my COM cable from the previous COM port on my StarterKit and put it on another. When trying to do SHIFT+ S in DCUTerm, I get this :
[IMG:http://oi61.tinypic.com/15wkq6x.jpg]

When using HyperTerminal, I get this :

[IMG:http://oi57.tinypic.com/1e7uc9.jpg]

Since it smells good that way, I'll stick with HyperTerminal. So after this, I get to follow chapter 9.7.1 of your document right ? Except I need to use DE instead of DU ?

When DE done, I can launch EShell and select my image and go like that ?

Ok, I plugged my NetDCU on my SKit and I've plugged in my COM cable.

I decided to use DCUTerm as a terminal and I was able to connect. I'm in the registry here, i'm able to type in command such as help, reg open, etc... If I understand well, this is called the NDCUCFG port and I need the serial debug port to enter EBoot and press the SHIFT+S that will allow me to enter the "DE" command, right ?

As a reminder my configuration is :
\: HKEY_LOCAL_MACHINE\System\NDCUCFG
00 "Port"=string:COM2: \

Quote from fs-support_ZU

But what is about a Workshop:-)
Maybe we waste here a lot of time.

Sorry, let me just clarify one thing. I'm losing much time because two times in a row FS-Net provided us with a card that is badly configured.

• Wrong Boot Firmware (very old version).
• Return with RMA, the overall process took roundly 6 weeks.
• The card returned with correct boot firmware but OS replaced with a wrong one (6.0 instead of 2013 or 7.0).
• We're receiving not a lot of efficient support, neither from our reseller, neither from FS-Net which gives us support only through this forum.
• I'm spending much time to understand how everything work and try and find solution to make your card work and you're proposing me to pay for a Workshop we never ever needed in 6-7 years of use of your last NetDCU8 (already bought at least 150 cards). I hardly think that's a fair deal for us to pay for a Workshop only to fix Fs-Net mistakes.

I hope my message is well heard.

Quote from fs-support_ZU

No, this is not "our" device - i assume. After enter "DE" im the bootloader a new deivice will be added, select this one.

You're right, it's not the card, it's indeed my device. When talking about device, I mean our device on which I plug my NetDCU. It provides me with an interface to a COM port and a Ethernet port. That's it.

Quote

On A5 boards "ndcucfg" and "debug port" located on COM1: by default. Enter <shift +s> into the termnal while power on the device for step into the bootloader.

Yes, I've faced this trouble because, on my device, we've linked our COM port to your COM2: port. I had to switch in the registry to have be able to use the COM port on my device.

I assume my last option is to use one StarterKit. I've just found a really old starter kit (that we had from our very first NetDCU8 I guess)... Is it worth the try ?

Quote from fs-support_ZU

Hello,

Yes, after enter DE in the bootlaoder your device will be recognized. Then select the image ... .

The device has already been recognized in the first window (Select Device in my previous post). Isn't it enough ?

My problem now is that, when my card is plugged on my device, I'm connected to COM2 and not COM1. If I understand well, COM1 is the port where the bootloader can be accessed.

So, when using DCUTerm, I can access the registry but I don't know how to access the bootloader from here...

Ok I'll give it a try using EShell...

I started EShell and It recognized my device displaying its Ethernet Name. When clicked on it it asks for an image... Do I have to enter the bootloader sideway with a COM port connection and press "DE" ?

[IMG:http://oi61.tinypic.com/2v9vrpw.jpg]

[IMG:http://oi59.tinypic.com/21dh7o8.jpg]

Do I risk doing something wrong by simply continuing that ?

So far from my investigation :

• I've found a software called EShell on my FS Page.
• I've found an image of the OS (in that case WinCE 2013) called XIPVYB_C8E_140414.bin. I guess that's the OS image I have to restore.
• I've found a documentation called "FSVYBRID WInCE Update instructions.pdf" but it talks about NBoot and EBoot update, and I don't need that I guess, since my card has been properly updated by FS on that side.
• I've found a documentation called "KernelUpdateUsingTheEShell_V100_eng.pdf" and I guess I should follow this one in order to update properly my OS, is it correct ?
• I understood that I could update the card using EShell through Ethernet connection. Is that correct ?

Thank for your quick answer, I definitely need a WinCE 2013/7 card as soon as possible !

Hi all,

I've returned a card with a RMA a few weeks ago because I faced a problem with the firmware version of my card which was really old. It's been properly upgraded by you but in the process, you changed the OS and put it back to WinCE 6.0. I definitely need your most up to date OS for the NetDCUA5 for tests purpose. Here are my questions :

I've read about WinCE 2013, WinCE 7.0. What are the differences ? Which one will receive the longer support from your side ? Do you recommend one over the other for some reasons ?

I have only a NetDCUA5 card in my possession. What do I need (hardware and software) in order to make the OS update? I don't have time to make another RMA (the last one took 5-6 weeks ! and I cannot afford to lose
that much time again)...

I guess I have to connect through USB to my card to update the OS. I only have COM and Ethernet connection on the device on which the card is plugged on. What is the fastest way to proceed ? Do I have to order a special USB cable or an adapter to connect on my card ?

Thanks for your reply.