Tiny210 512MB version

WinCE Guy

2012-11-20 00:47:24

Hi,

I just received a batch of Tiny210 modules and discovered that my NK.bin
doesn't work.  I'm still to get to the bottom of it but after looking over
the module I see the PCB revision is the same but the most obvious
difference is that the Nand Flash chip has twice the capacity of my earlier
ones.  My original ones were 256MB but the new ones are 512MB.

Anyway - my assumption is that the NandFlash.dll needs to be updated with
the correct parameters for the new flash chip.  But since there's no source
for this we can't do this ourselves.  

Does anyone have a working Wince 6 on the 512MB version of the Tiny210?

Some of the other BSP's floating around for the same processor do have
source for the nand flash driver so I may have to try and obtain one of
these and see if I can get it to work.  

I'm currently using the Tiny210-20120913 version of the supplied
FriendlyArm software.

dezso

2012-11-20 02:26:07

I would buy one if the 512 with 7"capacitive touch running CE7 in a flash. 
Anyone know if this will ever happen ?

WinCE Guy

2012-11-21 01:10:58

OK, so the problem is definitely the change in Flash memory size.

Does anyone have the actual source for the nandflash driver?  Note that the
files are in the BSP but if you try to build them they don't build due to
errors.

FriendlyArm provide us the Nandflash.dll in the FILES folder and have the
Nand source excluded from the build so they must want to keep the source
for the driver closed....

If anyone has a working version of the source even if it's for the 256MB
version I'd be most interested in seeing it.  Shouldn't be hard to modify
for the 512MB board.

armdevs

2012-11-21 03:44:26

Download the new BSP from the followe website:
http://armdevs.com/info194.html

The new update for the Mini210/Tiny210/Tiny210V2 for WiNCE in 2012-11-16:
Update Detail:Support 512MB Nand Flash and Capacitive screen in WInCE 6.0
Update Date: 2012-11-16

WinCE Guy

2012-11-21 06:41:11

Unfortunately this does not work.

I think the issue is that the Nandflash driver in the new BSP has been
updated to support the new Flash memory but has some bugs in it.  It does
recognise the larger flash chip yes, but it reports the wrong size to the
OS.

Here is a dump of the debug build of Mini210-en (using the new Mini210 BSP
from 16/11/2012 - 1246 )

I think the issue is shown in the line
"FSDMGR!StoreDisk_t::Mount:  Geometry:  NumSec=-79  BytesPerSec=1 
FreeSec=0  BiggestCreatable=0" where it reports a negative number for the
number or sectors and also 1 bytespersec.  

FSDMGR!PNPThread:  Using  PNPUnloadDelay  of  4096
NandMlc2Probe:  0
FSDMGR!StoreDisk_t::OpenDisk  (0xD0045060)  DeviceInfo  Class  (0x00000001)
 Flags  (0x00000005)  Type  (0x00000002)  Profile  (NANDFLASH)
FSDMGR!MountStore:  Attaching  new  storage  device 
"NANDFLASH"FSDMGR!DumpRegKey:  Dumping  registry  for  key 
System\StorageManager\Profiles
AutoMount  =  00000001
AutoPart  =  00000000
AutoFormat  =  00000000
MountFlags  =  00000000
DefaultFileSystem  =
PartitionDriverName  =  MSPART
Folder  =  Mounted  Volume
ActivityEvent  =  PowerManager/ActivityTimer/SystemActivity
FSDMGR!DumpRegKey:  Dumping  registry  for  key  NANDFLASH
Name  =  NANDFLASH
DefaultFileSystem  =  FATFS
PartitionDriver  =  flashpart.dll
Folder  =  NANDFlash
AutoPart  =  00000001
AutoFormat  =  00000001
AutoMount  =  00000001
MountFlags  =  00000000
MountAsBootable  =  00000001
FSDMGR!StoreDisk_t::GetPartitionDriver:  Using  the  generated  partition 
driver  name  (flashpart)!!!
Kernel  DLL  'flashpart.dll'  needs  thread  creation/deletion 
notification
FSDMGR!LoadPartitionDriver:  Loading  partition  driver  flashpart.dll 
hModule=9FF7AE40
FSDMGR!StoreDisk_t::Mount:  Opened  the  store  "NANDFLA" 
hStore=0xD0046180
FSDMGR!StoreDisk_t::Mount:  Geometry:  NumSec=-79  BytesPerSec=1  FreeSec=0
 BiggestCreatable=0
Exception  'Data  Abort'  (4):  Thread-Id=00600002(pth=9ffc0678), 
Proc-Id=00400002(pprc=83799aa0)  'NK.EXE', 
VM-active=0040000FSDMGR!PNPThread:  PNPThread  starting!
2(pprc=83799aa0)  'NK.EXE'
PC=c0689f34(flashmdd.dll+0x00029f34)  RA=c0689eb8(flashmdd.dll+0x00029eb8) 
SP=d00be2a4,  BVA=d0241000
FILESYS:  Starting  boot  phase  1.
FSDMGR!STOREMGR_StartBootPhase  BootPhase=1  (PrevBootPhase=0)
FSDMGR!AutoLoadFileSystems:  CurrentBootPhase=1,  LoadFlags=1
FILESYS:  Starting  device  and  waiting  for  boot  file  system.
***  DLL_PROCESS_ATTACH  -  Current  Process:  0x42,  ID:  0x400002  ***
Filesys:  Loaded  device.dll
FILESYS:  Waiting  for  device  manager  to  signal  BootPhase1 
completion.
+InitDeviceFileSystems
FSDMGR!MountTable_t::RegisterVolumeName:  Registered  "$device"  at  index 
5FSDMGR!MountTable_t::RegisterVolume:  Registered  volume  at  index  5 
(Name="$device",  MountFlags=0x1)FSDMGR!MountTable_t::RegisterVolumeName: 
Registered  "$bus"  at  index  6FSDMGR!MountTable_t::RegisterVolume: 
Registered  volume  at  index  6  (Name="$bus", 
MountFlags=0x1)-InitDeviceFileSystems:  status  is  1
Ceddk!CalibrateStallCounter:  Enter
Ceddk!CalibrateStallCounter:  Could  not  find  stall  counter
Ceddk!BeginCalibration:  min(12001)  max(13334)
Ceddk!BeginCalibration:  Elapsed  is  13296
Ceddk!BeginCalibration:  Delay  is  97
DEVICE!DevloadInit
DEVICE!InitDevices:  Root  Key  is  Drivers\BuiltIn.
DEVICE!RegReadActivationValues  RegQueryValueEx(Drivers\BuiltIn\Prefix) 
returned  2
DEVICE!RegReadActivationValues  RegQueryValueEx(Drivers\BuiltIn\BusPrefix) 
returned  2
DEVICE!RegReadActivationValues 
RegQueryValueEx(Drivers\BuiltIn\NANDFLASH\BusPrefix)  returned  2
DeviceFolder::LoadDevice(Drivers\BuiltIn\NANDFLASH)  last  8 
TicksDEVICE!RegReadActivationValues 
RegQueryValueEx(Drivers\BuiltIn\Drvlib\Prefix)  returned  2
DEVICE!RegReadActivationValues 
RegQueryValueEx(Drivers\BuiltIn\Drvlib\BusPrefix)  returned  2
DMSG:  DrvWAITInitialize
+  NKKernelLibIoControl
-  NKKernelLibIoControl
Kernel  DLL  'drvlib.dll'  needs  thread  creation/deletion  notification
DEVICE!CreateDevice:  illegal  entry  point  combination  in  driver  DLL 
'drvlib.dll'
CreateDevice:  creation  of  type  '<unnamed>',  index  0,  lib 
'drvlib.dll'  returning  0x00000000,  error  code  1
DEVICE!I_ActivateDeviceEx:  couldn't  activate:  prefix  <nil>,  index  0, 
dll  drvlib.dll,  context  0x1
DeviceFolder::LoadDevice(Drivers\BuiltIn\Drvlib)  last  55  TicksFILESYS: 
Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.
FILESYS:  Waiting  for  bootable  file  system  to  be  mounted.

armdevs.com

2012-11-21 10:21:14

Download the Wince system image with the follow website:
http://armdevs.com/info194.html

Notice, the superboot.bin in the SD card and the the board need to update
with the new verison.

You can download our system image file to update it with your 512MB flash.

WinCE Guy

2012-11-21 11:17:02

Yes it was the SuperBoot update that was needed.
Yesterday when FriendlyArm gave me the updated BSP I wish they had given me
the updated SuperBoot file at the same time.  It would have saved lots of
time!

Thank you for helping me out so quickly.