- Change USB Function driver to USBSER_Class: (\Drivers\USB\FunctionDrivers\Default = USBSER_Class)
- Connect the PicoMODA9 to a Computer
- Start DcuTermi.exe
- Open the COM Port of the PicoMODA9
-> Error 121
Posts by Festus
-
-
Can you reproduce it?
-
Do you have any new Information when this bug will be fixed?
I still would like to know if Roadmap entry 2772 (see above) is related to my Problems.
-
Any News?
-
I'm nearly (but not fully) 100% sure that Kernel V2.00 was already installed on Monday.
No, I never tested Audio because we do not use Audio, but Rev 1.00 is printed on the board.
There are different first exceptions:
Code- Exception 'Data Abort'(4) Thread-Id=03a70002(pth=bb461d00) PC=802626c8 BVA=00001000, dwInfo = 00000807
- R0=00000000 R1=eee5e5f8 R2=cc7d0000 R3=60860000
- R4=bb461d00 R5=cc7efce0 R6=00000000 R7=ffffc800
- R8=00000000 R9=00000001 R10=ffffc888 R11=ffffc824
- R12=ffffc800 SP=cc7efbd4 Lr=802626c8 PC=802626c8, Psr=2000001f
Code- Exception 'Undefined Instruction'(1) Thread-Id=07400152(pth=bb5e7750) PC=802626c8 BVA=0126effc, dwInfo = 00000807
- R0=00000000 R1=00000002 R2=6000011f R3=ffffc800
- R4=bb5e7750 R5=d6c9fca8 R6=00000000 R7=ffffc800
- R8=00000000 R9=00000002 R10=ffffc888 R11=ffffc824
- R12=ffffc800 SP=d6c9fb9c Lr=802626c8 PC=802626c8, Psr=2000011f
Code- Exception 'Prefetch Abort'(3) Thread-Id=021c0006(pth=bb46d7e0) PC=802626c8 BVA=d7e9efcc, dwInfo = 00000807
- R0=00000000 R1=00000002 R2=6000001f R3=ffffc800
- R4=bb46d7e0 R5=cc9bfcdc R6=00000000 R7=ffffc800
- R8=00000000 R9=00000001 R10=ffffc888 R11=ffffc824
- R12=ffffc800 SP=cc9bfbd0 Lr=802626c8 PC=802626c8, Psr=2000001f
But the program Counter is equal in all cases.
-
If you Need more Information, here are the registry Settings of our can bus:
Code- !>reg open \Drivers\builtin\picomoda9\can<LF>
- \: HKEY_LOCAL_MACHINE\Drivers\builtin\picomoda9\can
- OK
- !>reg enum<LF>
- OK -> reg enum key \
- OK -> reg enum value \
- 00 "TxMode"=dword:7 \
- 01 "SendbufferSize"=dword:100 \
- 02 "EventQueueSize"=dword:1000 \
- 03 "Priority256"=dword:50 \
- 04 "CanMode2B"=dword:0 \
- 05 "Virtualize"=dword:0 \
- 06 "MaskActive"=dword:0 \
- 07 "AcceptanceCode"=dword:0 \
- 08 "Format"=dword:0 \
- 09 "AcceptanceMask"=dword:2047 \
- 10 "Align"=dword:1 \
- 11 "Baudrate"=dword:500000 \
- 12 "Prefix"=string:CID \
- 13 "Dll"=string:FS_CANDRV.dll \
- 14 "Order"=dword:37 \
- 15 "Index"=dword:1 \
- 16 "Ioctl"=dword:4 \
- 17 "FriendlyName"=string:CAN interface \
- 18 "DeviceArrayIndex"=dword:0 \
- 19 "IOBaseAddr"=dword:34144256 \
- 20 "IRQ"=dword:142 \
- OK
By the way:
I now made a test with an external power supply of 3.3V and I had teh same watchdog reset. So I assume that the Problem is not caused by a weak power supply. -
Ok thanks,
no hint yet, sorry. It seems that code 8 Comes right after the can port was opened but that it takes a while until the other exceptions are raised.
-
Did you already had a Chance to look into this?
Yesterday afternoon, I again had a watchdog reset and again there was a debug Output CID: [0] (RX) Unexpected MB code 0x8.
But this time, there where a ot of
Code- Exception 'Undefined Instruction'(1) Thread-Id=07400152(pth=bb5e7750) PC=802626c8 BVA=0126effc, dwInfo = 00000807
- R0=00000000 R1=00000002 R2=6000011f R3=ffffc800
- R4=bb5e7750 R5=d6c9fca8 R6=00000000 R7=ffffc800
- R8=00000000 R9=00000002 R10=ffffc888 R11=ffffc824
- R12=ffffc800 SP=d6c9fb9c Lr=802626c8 PC=802626c8, Psr=2000011f
messages. I fount 26 Messages with "Undefined instruction" and 4 with "Data Abort" in the debug Output, the stack pointer (SP) Switches between d6c9fb9c and ffffxxxx (xxxx is different in every log message)
I do not think it will help when I append the full debug Output again, what do you think?
I'm not 100% sure, but I think that reading CAN Messages causes this Problem. If I run our application while the PicoMODA9 is not connected to our CAN bus, I didn't encounter a watchdog reset yet.
I really need help here.
-
Some additional Information: I just saw that I set the priority of the can Driver to 50, so it seems to be possible that the can Driver can cause the watchdog reset.
-
I tested RS232 RTS/CTS handshake with Kernel 2.00 but it still does not work.
Now I found another entry in the Roadmap for V2.10:
- 0002890: [Serial Driver/Interface] RTS/CTS does not work. - newI think, this will solve my RS232 Problems... nor not?
I still would like to know if Roadmap entry 2772 (see above) is related to my Problems.
-
(Continued because more than 10000 characters)
Code- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffff0a5c) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffb4f0 R3=00000000
- R4=ffff0c6c R5=80667980 R6=Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=10000006, dwInfo = 00000005
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffff0648) PC=ffff0cc5 BVA=10000006, dwInfo = 00000005
- R0=10000000 R1=fffe10e0 R2=ffffc888 R3=ffff2220
- R4=fffe10e0 R5=806655e0 R6=32af0000 R7=806655e0
- R8=00000000 R9=00000008 R10=00000004 R11=ffff0c28
- R12=ffff0870 SP=ffff0800 Lr=ffffc800 PC=ffff0cc5, Psr=20030072
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- Microsoft Windows CE Bootloader Common Library Version 1.2 Built Oct 9 2015 17:44:45
- Microsoft Windows CE Bootloader for PicoMODA9 Built Oct 9 2015
- Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
- Boot Loader, Version 1.20
- NBoot, Version VN25
- HW rev. 1.0
- HW-Watchdog: ON
- System ready!
- Preparing for download...
- Press >S< to step into monitor...
- AUTO BOOT enabled
- +ReadKernelRegionFromNandFlash
- Image Signature in Flash Memory found (dwSig=0x43454345)
- TOC pointer=0x8046596C
- ROMHDR (cTOC = 0x0024596c) ---------------------
- DLL First : 0x4001efd2
- DLL Last : 0x4013f000
- Physical First : 0x80220000
- Physical Last : 0x80560df8
- Num Modules : 34
- RAM Start : 0x80620000
- RAM Free : 0x8066c000
- RAM End : 0x941fc000
- Num Copy Entries : 2
- Copy Entries Offset : 0x80465ee0
- Prof Symbol Length : 0x00000000
- Prof Symbol Offset : 0x00000000
- Num Files : 8
- Kernel Flags : 0x00000001
- FileSys RAM Percent : 0x20202020
- Driver Glob Start : 0x00000000
- Driver Glob Length : 0x00000000
- CPU : 0x01c2
- MiscFlags : 0x0002
- Extensions : 0x80222208
- Tracking Mem Start : 0x00000000
- Tracking Mem Length : 0x00000000
- Kernel (3331kB) read from flash disk started finished in 0 milliseconds
- Kernel read from NAND
- INFO: OEMLaunch: Jumping to Physical Address 0x10220000h (Virtual Address 0x10220000h)...
- Jumping to Kernel @ 0x10220000
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- Windows CE Kernel for ARM (Thumb Enabled)
- g_vaL2CtrlBase=0xa0a02000
- Enabling L2 cache
- OEMInit: silicon rev = 0x12
- SMP support enabled
- PicoMODA9 V2.00 - Firmware Init
- Copyright (c) 2013 F&S Elektronik Systeme GmbH
- Build: Mar 1 2016/19:28:50
- OAL: Detected 2 CPUs
- OAL: Another CPU core started
- ERROR: OEMSetRealTime: NKSystemTimeToFileTime failed.
- [OAL] MACB: Disabled
- [OAL] RestartReason: WDOG
- FSPART: FS partition driver loaded
- BINFS: RegisterVolume - Mounted volume '\BINFS'
- PM-NETDCU: STARTED
- BE2: Version 1.4, ActiveKey = Drivers\Active\01
- BE2: Version 1.4, ActiveKey = Drivers\Active\04
- IPU: Version 1.4, ActiveKey = Drivers\Active\11
- PP: Version 1.1, ActiveKey = Drivers\Active\21
- VDI: Version 1.1, ActiveKey = Drivers\Active\22
- ENET: Version 1.3, ActiveKey = Comm\ETHNETA
- ETHMAN: Version 1.0, ActiveKey = Drivers\Active\32
- BE2: Version 1.4, ActiveKey = Drivers\Active\34
- Serial: Version 1.5, ActiveKey =
- Serial: Port disabled. Serial debug is on !
- Serial: Version 1.5, ActiveKey =
- TCH: Version 1.1, ActiveKey = Drivers\Active\38
- SHC: Version 1.3, ActiveKey = Drivers\Active\39
- SHC: Version 1.3, ActiveKey = Drivers\Active\40
- CID: Version 2.5, ActiveKey = Drivers\Active\41
- NSPI: Version 3.7, ActiveKey = Drivers\Active\42
- SGTL Open I2C failed
- PPU: Version 1.1, ActiveKey = Drivers\Active\44
- DIO: Version 1.4, ActiveKey = Drivers\Active\45
- SHC: [USDHC1] SD card inserted
- FRW: Version 1.3, ActiveKey = Drivers\Active\51
- GALCORE 4.6.9(9754) (Sep 19 2014 12:09:40)
- Major GPU: SysIntr=26 MemBases=0x130000 MMU Version=0
- 2D GPU: SysIntr=27 MemBases=0x134000 MMU Version=0
- Video memory: BaseAddress=0x0 PhysBase=0x106d1000 size=0x7000000 physSize=0x0
- LCD: Version 1.1, ActiveKey = Drivers\Display\LCD
- LCD: Read registry settings from Drivers\Display\LCD
- LCD: Read registry settings from Drivers\Display\LCD
- LCD: Display-Mode 100, Name Hitachi TX14D11VM1
- TCH: Could not enable touch panel
- NDCUCFG V 64 started. Platform: PicoMODA9
- NDCUCFG Open COM1: at 115200 Baud
- CreateFile() failed -> ERROR COM1:
- CheckAutoStart: Version 1.7, LaunchNum = 100
- ENET: LinkState: DISCONNECTED
- Explorer(V2.0) taskbar thread started.
- BCS: Version 1.4, ActiveKey = Drivers\Active\72
As you can see, thare a a lot of exceptions in Thread 065002ee (No idea what this thread does or if that thread is one of out application threads)
-
I think I have to correct myself.
I also did a test over the Weekend with a PicoMODA9 without any application running (Explorer was shown) and didn't had a watchdog reset.
But today, I again had a watchdog reset while our applicacation was running.
I now think that the Problem is caused by CAN bus communication.Here is the bootlog (fetched by DCU-Termi.exe):
Code- ing IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMTYPE, which has been deprecated. Use IOCTL_HAL_GET_DEVICE_INFO::SPI_GETPLATFORMNAME instead.
- AppConfig Barcode is null
- AppConfig Barcode is null
- CID: [0] (RX) Unexpected MB code 0x8 <----- What is this?
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- 01/01/2006 13:48:52 BLACKBOXDATA SAVED
- 01/01/2006 13:49:02 BLACKBOXDATA SAVED
- CID: CID_IOControl(0x10303ff) failed, error=120
- CID: CID_IOControl(0x10303ff) failed, error=120
- CID: CID_IOControl(0x10303ff) failed, error=120
- CID: CID_IOControl(0x10303ff) failed, error=120
- AppConfig DataMatrixCode is null
- AppConfig DataMatrixCode is null
- 01/01/2006 13:52:32 BLACKBOXDATA SAVED
- 01/01/2006 13:52:41 BLACKBOXDATA SAVED
- Exception 'Prefetch Abort'(3) Thread-Id=065002ee(pth=bb532270) PC=802626c8 BVA=c99201db, dwInfo = 00000807
- R0=00000001 R1=bb497550 R2=ffffc828 R3=00000000
- R4=bb532270 R5=d7d1fac0 R6=00000000 R7=ffffc800
- R8=00000000 R9=00000001 R10=ffffc888 R11=ffffc824
- R12=ffffc800 SP=d7d1f9b4 Lr=802626c8 PC=802626c8, Psr=2000011f
- Exception 'Prefetch Abort'(3) Thread-Id=065002ee(pth=ffffc5cc) PC=a0a00000 BVA=c99201db, dwInfo = 00000807
- R0=00000001 R1=00000003 R2=00000001 R3=80626850
- R4=20000113 R5=80626050 R6=dffffeed R7=00519b91
- R8=80668094 R9=00000001 R10=8066501c R11=ffffc888
- R12=ffffc834 SP=ffffc798 Lr=a0a00000 PC=a0a00000, Psr=60000113
- Exception 'Prefetch Abort' (0x3): Thread-Id=065002ee(pth=bb532270), Proc-Id=00400002(pprc=806655e0) 'NK.EXE', VM-active=068202ee(pprc=bb5d7390) '6.750.7130.exe'
- PC=a0a00000(???+0xa0a00000) RA=a0a00000(???+0xa0a00000) SP=ffffc798, BVA=a0a00000
- Exception 'Data Abort' (0x4): Thread-Id=065002ee(pth=bb532270), Proc-Id=068202ee(pprc=bb5d7390) '6.750.7130.exe', VM-active=068202ee(pprc=bb5d7390) '6.750.7130.exe'
- PC=420dc8b8(mscoree3_5.dll+0x0004c8b8) RA=420dd838(mscoree3_5.dll+0x0004d838) SP=0219ed4c, BVA=0219ed88
- Exception 'Data Abort' (0x4): Thread-Id=065002ee(pth=bb532270), Proc-Id=068202ee(pprc=bb5d7390) '6.750.7130.exe', VM-active=068202ee(pprc=bb5d7390) '6.750.7130.exe'
- PC=80259724(kernel.dll+0x0000f724) RA=8025a148(kernel.dll+0x00010148) SP=d7d1fba0, BVA=0219eb8c
- !!! Committed last page of the stack (0x0219ed88) or invalid stack pointer (0x0219ed4c), SEH bypassed, thread terminated !!!
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=fffffff8, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffc32c) PC=8025b7fc BVA=fffffff8, dwInfo = 00000007
- R0=00000001 R1=00000004 R2=00000000 R3=8022d9ec
- R4=d7d1dec8 R5=80667980 R6=80667980 R7=d7d1d000
- R8=00000807 R9=d7d1df5c R10=00000004 R11=d7d1df58
- R12=80665214 SP=ffffc4f8 Lr=80263548 PC=8025b7fc, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffc098) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e118 R3=00000000
- R4=ffffc2a8 R5=80667980 R6=ffffc418 R7=00000001
- R8=ffffc468 R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffc264 Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffbe04) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffc468 R3=00000000
- R4=ffffc014 R5=80667980 R6=ffffc184 R7=00000001
- R8=ffffc1d4 R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffbfd0 Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffbb70) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffc1d4 R3=00000000
- R4=ffffbd80 R5=80667980 R6=ffffbef0 R7=00000001
- R8=ffffbf40 R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffbd3c Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffb8dc) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffbf40 R3=00000000
- R4=ffffbaec R5=80667980 R6=ffffbc5c R7=00000001
- R8=ffffbcac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffbaa8 Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffb648) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffbcac R3=00000000
- R4=ffffb858 R5=80667980 R6=ffffb9c8 R7=00000001
- R8=ffffba18 R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffb814 Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffffb3b4) PC=8025af90 BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=ffffba18 R3=00000000
- R4=ffffb5c4 R5=80667980 R6=ffffb734 R7=00000001
- R8=ffffb784 R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=ffffb580 Lr=8025af40 PC=8025af90, Psr=60000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=ffff114c, dwInfo = 00000807
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffff0f0c) PC=80258828 BVA=ffff114c, dwInfo = 00000807
- R0=ffff114c R1=00000004 R2=60000193 R3=ffffc800
- R4=065002ee R5=80667980 R6=00000004 R7=00000007
- R8=00000008 R9=00000008 R10=00000004 R11=ffffb2ec
- R12=ffffb0a8 SP=ffff10d8 Lr=80252244 PC=80258828, Psr=60000193
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=ffff1088, dwInfo = 00000807
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=ffff0cf0) PC=8025b85c BVA=ffff1088, dwInfo = 00000807
- R0=00000002 R1=00400002 R2=00000013 R3=ffff10d8
- R4=ffff1048 R5=80667980 R6=ffff0f0c R7=80258828
- R8=00000807 R9=ffff114c R10=00000004 R11=ffff10d8
- R12=aa33ffc7 SP=ffff0ebc Lr=00000000 PC=8025b85c, Psr=80000113
- Exception 'Data Abort'(4) Thread-Id=065002ee(pth=80667980) PC=80258f2c BVA=00000008, dwInfo = 00000007
- R0=80667980 R1=00000000 R2=d7d1e640 R3=00000000
- R4=d7d1e1ec R5=80667980 R6=d7d1e35c R7=00000001
- R8=d7d1e3ac R9=00000000 R10=00000000 R11=0000001f
- R12=ffffc800 SP=d7d1df58 Lr=8025af40 PC=80258f2c, Psr=6000011f
-
I have BoardRevision 100
-
How could a weak power supply cause a watchdog reset???
-
But 2797 is listed as resolved in V1.80?!
-
I just saw that V2.00 was released but I think there is a Problem with the zip file (when I try to unzip it, I get an error message that the zipped foler is invalid).
The zip file of the new kernel also is only 1,1MB large. The last one had ~26MB. -
I didn't has any application running when the reset occured.
Just the Explorer was active.No I didn't has a chance to reproduce it and no I do not have any Serial debug Output (I didn't expect that I have to log the debug Output because I did not have any running application).
-
I had a Watchdog reset on my PicoMODA9 (see attached Picture of Remote Registry Editor).
What can cause this? Can you use the SRC_SRSR (=16) entry to determine what causes the watchdog reset? -
-
Sounds good, but actually the Roadmap entry (0002626) is listed for Version 2.10 (although the scheduled release of 2.10 is only one day later as 2.00)