Abort in Kernel during Filer_Boot

I’ve not seen this occur on RC14, but have now had a few occurances of the Kernal Aborting when processing a Filer_Boot I’ve issued via OS_CLI on the 15-10-15 Pi build.

Abort on Data Transfer at &FC015BA4
Address &FC015BA4 is at offset &00015BA4 in the Kernel

FC015B60 : E592A000 : LDR     R10,[R2,#0]
FC015B64 : E35A0000 : CMP     R10,#0
FC015B68 : 108AA00B : ADDNE   R10,R10,R11
FC015B6C : E10FE000 : MRS     R14,CPSR
FC015B70 : E38EE083 : ORR     R14,R14,#&83       
FC015B74 : E3CEE040 : BIC     R14,R14,#&40       
FC015B78 : E121F00E : MSR     CPSR_c,R14
FC015B7C : E702A00B : STR     R10,[R2,-R11]
FC015B80 : EA000005 : B       &FC015B9C
FC015B84 : E10FE000 : MRS     R14,CPSR
FC015B88 : E38EE083 : ORR     R14,R14,#&83       
FC015B8C : E3CEE040 : BIC     R14,R14,#&40       
FC015B90 : E121F00E : MSR     CPSR_c,R14
FC015B94 : E582A004 : STR     R10,[R2,#4]
FC015B98 : E082200A : ADD     R2,R2,R10
FC015B9C : E4823004 : STR     R3,[R2],#4
FC015BA0 : E49D3004 : LDR     R3,[R13],#4
FC015BA4 > E328F202 : MSR     CPSR_f,#&20000000
FC015BA8 : EAFFFF3D : B       &FC0158A4
FC015BAC : E5912008 : LDR     R2,[R1,#8]
FC015BB0 : E082B003 : ADD     R11,R2,R3
FC015BB4 : E591A00C : LDR     R10,[R1,#12]
FC015BB8 : E10FE000 : MRS     R14,CPSR
FC015BBC : E38EE083 : ORR     R14,R14,#&83       
FC015BC0 : E3CEE040 : BIC     R14,R14,#&40       
FC015BC4 : E121F00E : MSR     CPSR_c,R14
FC015BC8 : E15B000A : CMP     R11,R10
FC015BCC : 9581B008 : STRLS   R11,[R1,#8]
FC015BD0 : 90822001 : ADDLS   R2,R2,R1
FC015BD4 : 9AFFFFF0 : BLS     &FC015B9C
FC015BD8 : E24F0C02 : ADR     R0,&FC0159E0
FC015BDC : E240009C : SUB     R0,R0,#&9C         

Sadly I can’t provide a register dump as the Wimp gets into an endless “Abort on Data Transfer” loop.

The application being booted contains the following !Boot Obey script:

IconSprites <Obey$Dir>.!Sprites

EDIT: It does occur on RC14

Are you able to connect a serial cable to your Pi? With the number of odd aborts you’re seeing it would be good if I could send you a build that would output a stack dump over the serial port whenever something goes wrong.

I think I have a USB serial port somewhere, or can certainly purchase one. Does it need to be a specific model?

I’m not so certain I have another device to attach to the other end though, unless you can go Pi→Pi

There are serial RX & TX lines on the expansion header – it’s those which you’ll need to connect to. If you have cables which will fit the pins on the expansion header then you could probably just connect the RX, TX, and GND of the two Pi’s together (remembering to cross over the RX & TX lines!). If not, you should be able to pick up a generic USB serial adapter and have the USB side connected to a PC or something.

http://elinux.org/RPi_Serial_Connection

If you have the wires to connect the two pi serial pins I have a very basic (written in BASIC) serial terminal which runs in a taskwindow which reads serial output on a pi. I also have the same program modified to use a USB cp2102 ttl serial converter similar to this which I use to get output to my Iyonix or laptop. Just say if they would be any use.

If you haven’t got the cables to directly connect the two PIs the cables that come with the above serial device would do the trick.

I’ve just had this occur on RC14, which reported “Not a Heap Block” prior to the endless Abort loop. So there’s possibly a bug around an OS_Module 7 in the Kernel somewhere.