Posts by dhovden

To get version info, F&S said this "Enabel debug Output then you see this info:". Noone said where so I tried Eboot with the following result

:> O
Disable serial debug ouput during boot [Y] (Y/N) ? :N
> Debug output enabled
ReadBlock: failed to read sector (0x500).
WriteData: failed to read block (0x14).
ERROR: WriteEbootConfig: Flash write failed.
WARNING: MainMenu: Failed to store updated bootloader configuration to flash.

Not too promising unfortunately. Seems to be something wrong with the Flash.

What you got was the entire output.

And since DU now works in EBoot (and previously it didn't) I suppose it has been saved.

Erasing flash means that registry and everything is gone? That means I have to build my config again from scratch?
If so, that's a lot of work ...

I'm using the latest from your site. In the case of EBoot it's hard to know since it shows no version info, all it says is 'PicoComA5 - WindowsCE Bootloader'. For NBoot, it says 'VN05 Sp 12 2013'

One step further, entering 'du' in the Eboot loader caused device to be installed for FSBoardUSB. After that NetDCU USBloader showed a green light for USB connection so I started kernel download (131204 kernel) but that didn't go well

:> du
Waiting for USB download
Connected at high-speed
Connected at high-speed

Download file information:
-------------------------------------------------------------------------------
[0]: Address=0x80100000 Length=0x224ED70 Name=C:\Users\dag\Documents\Visual Studio 2008\Projects\MicroClimer\Docs\NKVYB_CE6Core_131204.bin
INFO: Changed start address for C:\Users\dag\Documents\Visual Studio 2008\Projects\MicroClimer\Docs\NKVYB_CE6Core_131204.bin to 0x80100000.
-------------------------------------------------------------------------------
##############################################################################################################################################################################################################################################################################################################################################################################################################################1 files tranfered
INFO: Write image at 0x80100000 size 0x0224ed70 to NAND Flash
Create partition for boot section ...
Success
Create partition for kernel section ...
Success
Create partition for FFSDISK section ...
Success
WriteRegionsToNandFlash
Writing single region/multi-region update, dwBINFSPartLength: 35974512
INFO: BP_OpenPartition: dwBINFSPartLength =0x224ED70).
dwRegionStart=0x80100000).
dwRegionLength=0x224ED70).
INFO: BP_SetDataPointer: Set data pointer in BINFS partition (offset=0x0).
INFO: WriteRegionsToNandFlash: Write region to BINFS partition (start=0x80100000, length=0x224ED70).
ReadBlock: failed to read sector (0x580).
WriteData: failed to read block (0x16).
ERROR: WriteRegionsToNandFlash: Failed to write region to BINFS partition (start=0x80100000, length=0x224ED70).
AUTO-BOOT enabled

ERROR: Flash write failed
HALT Reason=0xFFFFFFF4
ERROR: FlashWrite failed
ERROR !!!!
Disable AUTO BOOT
ReadBlock: failed to read sector (0x500).
WriteData: failed to read block (0x14).
ERROR: WriteEbootConfig: Flash write failed.
Reboot system and correct bootloader settings
SpinForever...

Here are the bootlaoder settings, don't see that anything is wrong with them

PicoCOMA5 boot options valid : YES
Start Download after reboot : no
Download kernel to : FLASH
Kernel load/store compression : OFF
Size of area for OS image : 64 MB
Size of FFSDISK : 64 MB
Format of FFSDISK : FAT
F3S serial number :
Launch image after reboot : yes
Output debug messages at serial port : no
Bootloader Network setting valid : YES
-MAC Address : 0:5:51:7:4D:22
-Use DHCP to get IP address: YES
WindowsCE MAC address valid : yes
-WindowsCE MAC Address : 0:5:51:7:4D:22

Yep, you starter interface. And yes, USB works except when I boot to EBoot. I can normally see the board as a drive in Explorer. Developing and debugging with VS2008 works as well.

Well, it doesn't matter what I do, any kernel other than 130910 hangs on 'Jumping to kernel'.
And DU still doesn't work because USB not enabled when booting to EBoot.

It seems to me that the downloading of neither NBoot nor EBoot works. The download itself works but after reboot nothing seems to have changed. And why is there no version info in the Eboot interface?

But NBoot is latest version already, it says "VN05 built 12 Sep 2013" when I boot and the file on your website, nbootvyb_05.zip, contains 12-9-13 files with postfix _05, so same version.

The zip file contains two files, nbootvyb_05.bin and nbootvyb115_05.bin, and nothing to tell the user which one to use or what the differences are. In fact, I don't know which one I'm using. So which one should I use?

I have now downloaded EBOOTVYB_06 twice, once serial and once over USB (USB is active when the NBoot loader is active) but although the download seems to work, DU still doesn't work and, I see now, gives the same error message. Somehow, the EBOOT loader isn't replaced.

Part of the problem is that the EBoot loader gives no version info or anything on startup so it's hard to know whether an upgrade has worked.

So, in the mean time, I'm back to kernel 130910 and no RTS support and quite unhappy with F&S.

OK, so I have upgraded EBoot and DU now seems to work. But when I run NetDCUUSBLoader, the USB LED never turns green so still can't download kernel that way. When rebooting the PicoCom with S pressed, going into EBoot, the USB connection sound isn't heard.

Downloaded the very latest, 131204, kernel but still hangs on 'Jumping to Kernel' so upgrading the EBoot didn't help any.

I really don't understand why this has to be so difficult every time ...

As far as I know, NetDCUUSBLoader cannot be used with the PicoComA5 I have because command 'DU' isn't supported, gives an error message when executed, reported before. I use DE and CEDownloader.

I have downloaded the latest kernel, CE6Core_131115 but when I send that to the PicoCom, I get to "Jumping to kernel ..." and then nothing happens. A reboot produces a white screen. So I transfer the 130910 kernel instead and everything works. So it seems that the latest kernel isn't working properly on the PicoComA5 ...

My board is a PicoComA5 and the kernel is 0.08 (10 sep 2013).
I toggle, as mentioned in my post, the RTS line with SerialPort.RtsEnable

Using VB.NET, I toggle SerialPort.RtsEnable. Having a scope connected to pins 4 (RTS) and 9 (GND) on J6 I would expect to see the pin go high/low as I toggle. Instead, nothing at all happens on pin 4. Why is that?

In <!-- m --><a class="postlink" href="http://www.fs-net.de/download/docu/common/english/DeviceDriver_FSS5PV210_FSVYBRID_WIN_eng%20.pdf">http://www.fs-net.de/download/docu/comm ... eng%20.pdf</a><!-- m --> several devices are described, among them the PicoComA5. But whereas there is a port description for devices such as PicoMOD, QBliss, etc I can't find one for the PicoComA5.

I don't see how I can figure out how to set UseAsIO etc without this documentation. Or is the A5 the same as the PicoCom4 when it comes to ports?

Regards,
Dag

Could not get EShell do to do anything at all.Finally managed to download CE6 with CEDownloader, worked straight away.
Have patched VS but doesn't work with CE7 - does work with CE6 so I'll stick to that.

Dear F&S Elektronik Systeme

Could I please have a response on this topic, one that doesn't just say "it works for me"!!

Summary of problem:

1) With CE7 kernel, cannot connect with VS2008 (can see board with Explorer)
2) Cannot install CE6 kernel because 'du' gives error message (see my other post)
3) Cannot install CE6 kernel with 'de' because eshell doesn't seem to work

Regards,
Dag Hovden

Dear F&S Elektronik Systeme

I would very much appreciate a reply to this topic since I'm currently stuck. I find it quite strange that you market a new board and then provide so little support for the problems some, like me, will have.

Regards,
Dag Hovden

Checked that my VS2008 is up to date - it is.
Tried to connect with a PicoCom4 board - worked straight away.
Tried to download CE6 image to A5 board instead - got an error message entering 'du' in EBoot
Stuck! And not impressed with F&S tools and docs

Trying to install a new kernel (CE6 instead of EC7) to my PicoComA5 and nothing works:
Note: the board came with EC7 preinstalled

1) holding down shift+s does not enter the EBoot loader, instead it goes to NetDCU config utility
2) holding down s does enter NBoot so I used that to download an EBoot image

Sidenote: how can I possibly know if I should follow the instructions in the PDF file "Update instructions for F&S Vybrid based boards." to update NBoot and EBoot???
Just so confusing!!

3) Now entering EBoot works so I type du only to get

:> du
BLUsbDownload() not implemented yet
EbootUSBReadData() not implemented yet

Unable to read image signature.
HALT Reason=0xFFFFFFF8
ERROR: not a BIN file
ERROR !!!!
Disable AUTO BOOT
Reboot system and correct bootloader settings
SpinForever...
+msWait: 1ms
+msWait: 0ms
+msWait: 0ms

It tells me to disable AUTOBOOT but how do I do that?

4) So I tried 'de' and EShell, no surprises there: didn't work at all, nothing happened in EShell

When installing the PicoCom3 some year ago it was exactly the same: nothing worked, the documentation was never really correct, only with the help of this board did I get everything running. And now the same thing again - why does it have to be so hard just to get the board ready for development??

Regards,
Dag

Hello,

I'm running CE7, should that make a difference?
What I find strange is that everything works, also the ActiveSync connection, allowing me to browse files on the PicoCom, but not Remote Tools and not VS2008. You would think that VS2008 also would make use of the ActiveSync connection.

Is CE7 better in any way when compared to CE6? Otherwise I'd be happy to go back to CE6 and install that kernel. The CE7 kernel was pre-installed.

Regards,
Dag