Have seen the following booting error from SH4 ?

We have a our own Board with Hitachi SH4 7750 that almost looks alike the
solution engine.
So we customized the startup (startup-sengine) for our B/D.
and also made a boot image including the our startup for our B/D.
Now we download the boot image to RAM and run it from a Monitor program.
We got the following debug messages and our B/D was shutdown.
I think the kernel may be crashed.

Does anyone have experiences like this ?
Thanks so much in advance.

Sangwoon Chung
swchung@rtsolutions.co.kr
http://www.rtsolutions.co.kr http://www.qnx.co.kr


The following is the debug messages from booting and the attached is our
build file for our B/D.

shdr->flags1 : 0

shdr->machine : 42

shdr->ram_size : 000b5b08d

shdr->signature : 00ff7eebd

Header size=0x0000009c, Total Size=0x00000628, #Cpu=1, Type=5

Section:system_private offset:0x000001b8 size:0x00000068

Section:qtime offset:0x00000128 size:0x00000048

Section:callout offset:0x000000a0 size:0x00000048

Section:cpuinfo offset:0x00000170 size:0x00000020

Section:cacheattr offset:0x000005e8 size:0x00000040

Section:meminfo offset:0x00000220 size:0x00000050

Section:asinfo offset:0x00000368 size:0x00000180

Section:hwinfo offset:0x00000300 size:0x00000068

Section:typed_strings offset:0x00000270 size:0x00000028

Section:strings offset:0x00000298 size:0x00000068

Section:intrinfo offset:0x000004e8 size:0x00000100

Section:boxinfo offset:0x00000190 size:0x00000028


System page at phys:0c001000 user:0c001000 kern:8c001000

Starting next program at v8c423c18

starting jump to Kernel…



Shutdown[0,0] S/C/F=10/1/5 C/D=8c40e080/8c44aa3c state(c0)= now lock

[0]PID-TID=1-2? P/T FL=00019001/00220000

shle context[8c00a158]:

0000: 00000000 73ff9307 43150009 8c447ad0 00000000 8c44a700 00000000
00000000

0020: 00000000 8c002d48 8c004618 00000000 8c004618 00000000 8c00a1b0
8c00a1b0

0040: 40008000 8c42c790 00000000 00000000 00000000 8c42cc1e

instruction[8c42c790]:

03 8d 12 22 42 62 41 51 11 12 43 61 09 71 10 61 13 60 0c 60 08 40 0c 30 53
62

stack[8c00a1b0]:

0000: 8c42cc1e 8c00a1b8 8c42f594 8c00a1c4 8c004694 8c004618 00000001
00000001

0020: 8c42e9e6 8c438460 8c00a1f0 8c004618 8c002d48 00008000 00000000
8c004618

0040: 8c4269b4 00000000 00000000 8c004618 8c0046cc 00008000 00000000
000000c0

0060: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000



begin 666 img4mbc.dat
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C"B,(R!.975T<FEN;R!O
M;B!A($AI=&%C:&D@4V]L=71I;VX@16YG:6YE(&5V86QU871I;VX@8F]A<F0

M(PHC(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,“EMI;6%G93TP>#AC
M-# P,# P70I;<&AY<VEC86P]<VAL92]B:6YA<GE=(“YB;V]T<W1R87 @/2![
M”@DN+B]S8W)A=&-H+W-H;&4O8F]O=”]S>7,O<W1A<G1U<"US96YG:6YE(“U$
M(’-C:2XN,S@T,# @+79V(“U3”@E0051(/2]P<F]C+V)O;W0@<’)O8VYT;R M
M=G9V=@I]”@I;W-C<FEP=%T@+G-C<FEP=" ]('L"61E=F,M<V5R<V-I("UE
M(’-C:68@<V-I("8
"7)E;W!E;@H)9&ES<&QA>5]M<V<@5V5L8V]M92!T;R!.
M975T<FEN;R!O;B!A(%-O;'5T:6]N16YG:6YE(&)O87)D"@D*“5LK<V5S<VEO
M;ET@4$%42#TZ+W!R;V,O8F]O=”!E<V@@)@I]"@I;='EP93UL:6YK72 O9&5V
M+V-O;G-O;&4]+V1E=B]S97(Q"EMT>7!E/6QI;FM=("]T;7 ]+V1E=B]S:&UE
M;0I;=‘EP93UL:6YK72 O=7-R+VQI8B]L9’%N>“YS;RXR/2]P<F]C+V)O;W0O
M;&EB8RYS;PIL:6)C+G-O”@I;9&%T83UC70ID979C+7-E<G-C:0IP:61I;@IU
2;F%M90IE<V@;’,<VQE97 *
`
end

“Sangwoon Chung” <swchung@rtsolutions.co.kr> wrote in
news:a3a7ta$5jn$1@inn.qnx.com:

We have a our own Board with Hitachi SH4 7750 that almost looks alike
the solution engine.
So we customized the startup (startup-sengine) for our B/D.
and also made a boot image including the our startup for our B/D.
Now we download the boot image to RAM and run it from a Monitor
program. We got the following debug messages and our B/D was shutdown.
I think the kernel may be crashed.

You’re not specifying the [physical] attribute in your build file are you?
If so, you need to use the [virtual] attribute. Perhaps you can post your
build file so we can all take a peek.

-Adam


Shutdown[0,0] S/C/F=10/1/5 C/D=8c40e080/8c44aa3c state(c0)= now lock

[0]PID-TID=1-2? P/T FL=00019001/00220000

shle context[8c00a158]:

0000: 00000000 73ff9307 43150009 8c447ad0 00000000 8c44a700 00000000
00000000

0020: 00000000 8c002d48 8c004618 00000000 8c004618 00000000 8c00a1b0
8c00a1b0

0040: 40008000 8c42c790 00000000 00000000 00000000 8c42cc1e

instruction[8c42c790]:

03 8d 12 22 42 62 41 51 11 12 43 61 09 71 10 61 13 60 0c 60 08 40 0c 30
53 62

stack[8c00a1b0]:

0000: 8c42cc1e 8c00a1b8 8c42f594 8c00a1c4 8c004694 8c004618 00000001
00000001

0020: 8c42e9e6 8c438460 8c00a1f0 8c004618 8c002d48 00008000 00000000
8c004618

0040: 8c4269b4 00000000 00000000 8c004618 8c0046cc 00008000 00000000
000000c0

0060: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000

“Adam Mallory” <amallory@qnx.com> wrote in message
news:Xns91AB6AEB3FB11amalloryqnxcom@209.226.137.4

“Sangwoon Chung” <> swchung@rtsolutions.co.kr> > wrote in
news:a3a7ta$5jn$> 1@inn.qnx.com> :

We have a our own Board with Hitachi SH4 7750 that almost looks alike
the solution engine.
So we customized the startup (startup-sengine) for our B/D.
and also made a boot image including the our startup for our B/D.
Now we download the boot image to RAM and run it from a Monitor
program. We got the following debug messages and our B/D was shutdown.
I think the kernel may be crashed.

You’re not specifying the [physical] attribute in your build file are you?
If so, you need to use the [virtual] attribute. Perhaps you can post your
build file so we can all take a peek.

Hi Adam,
Thank for your reply.

Unfortunately I did specify the [physical] attribute in my build file
attached.
because our Board could not configured with MMU mode for some reasons.

But for some time we have to test it with Non-MMU mode.

I know the docs for “mkifs” say that the physical attribute isn’t currently
supported.
The “mkifs” really does NOT support physical attribute now?

Thanks,
Sangwoon



begin 666 img4mbc.build
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C"B,(R!.975T<FEN;R!O
M;B!A($AI=&%C:&D@4V]L=71I;VX@16YG:6YE(&5V86QU871I;VX@8F]A<F0

M(PHC(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,“EMI;6%G93TP>#AC
M-# P,# P70I;<&AY<VEC86P]<VAL92]B:6YA<GE=(“YB;V]T<W1R87 @/2![
M”@DN+B]S8W)A=&-H+W-H;&4O8F]O=”]S>7,O<W1A<G1U<"US96YG:6YE(“U$
M(’-C:2XN,S@T,# @+79V(“U3”@E0051(/2]P<F]C+V)O;W0@<’)O8VYT;R M
M=G9V=@I]”@I;W-C<FEP=%T@+G-C<FEP=" ]('L"61E=F,M<V5R<V-I("UE
M(’-C:68@<V-I("8
"7)E;W!E;@H)9&ES<&QA>5]M<V<@5V5L8V]M92!T;R!.
M975T<FEN;R!O;B!A(%-O;'5T:6]N16YG:6YE(&)O87)D"@D*“5LK<V5S<VEO
M;ET@4$%42#TZ+W!R;V,O8F]O=”!E<V@@)@I]"@I;='EP93UL:6YK72 O9&5V
M+V-O;G-O;&4]+V1E=B]S97(Q"EMT>7!E/6QI;FM=("]T;7 ]+V1E=B]S:&UE
M;0I;=‘EP93UL:6YK72 O=7-R+VQI8B]L9’%N>“YS;RXR/2]P<F]C+V)O;W0O
M;&EB8RYS;PIL:6)C+G-O”@I;9&%T83UC70ID979C+7-E<G-C:0IP:61I;@IU
2;F%M90IE<V@;’,<VQE97 *
`
end

“Sangwoon Chung” <swchung@rtsolutions.co.kr> wrote in
news:a3odkf$e08$1@inn.qnx.com:

Unfortunately I did specify the [physical] attribute in my build file
attached.
because our Board could not configured with MMU mode for some reasons.

That’s a problem, since Neutrino requires the use of the MMU.

I know the docs for “mkifs” say that the physical attribute isn’t
currently supported.
The “mkifs” really does NOT support physical attribute now?

Neutrino doesn’t run without the MMU, so while mkifs does create the image,
it’s not very useful.


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>