eePe or er9X problem?

[mgros]

I have instaled the new revision of er9x R758 er9x-frsky version.

As usual i have changed splash screen but after installation the FW doesn't work properly.
Installing the FW without screen modification works OK.
In eePe if i try to "load from HEX" splash image for the new donloaded version only have a noise screen. (see image)

any other have the same effect?

[MikeB]

Bother, I'm doing some changes towards using a more recent compiler, that produces code 1500 bytes smaller, but the current compiler now decides to 'optimise out' the marker to the splash screen. I've worked out a temporary fix, but we will need a better one to make sure this doesn't happen again.

Mike.

[erazz]

Told ya 4.7 was weird.

[gohsthb]

It does it with my compiled hex too though. gcc 4.5.3. So like Mike said the marker must be lost.

I tried using gcc 4.7 to see what might happen different. When I do the above in eepe, Not only do I get the static, but I get to see the letters and numbers also! I'm sure you guys will have this sorted in a revision or 2.

-Gohst

[MikeB]

For those compiling themselves, add:

extern const prog_uchar APM s9xsplashMarker[] ;
extern const prog_uchar APM s9xsplash[] ;

as two consecuetive lines in er9x.h. This seems to force the compiler to include the marker AND put it just before the splash screen image.

I think, to be sure it works, we need to make the marker and the image part of the same object. Easy to do if I edit the s9xsplash.lbm file, but then it won't be correct if produced by ruby. I've never bothered with ruby as the .lbm files are under svn anyway.

Mike.

[ReSt]

It works with those two lines (and the old compiler)

Reinhard

[erazz]

I don't much like Ruby either. Can't understand the syntax.

Problem is that if you make it a part of the same structure you will have to modify the code to pass that part of the structure. Or do you intend to create a stuct to hold both variables?

[MikeB]

It's only referenced in one place (dosplash()), so that reference can be fixed to go to the correct place. I couldn't seem to get a struct to initialise without changing the included files anyway, so I'll probably just create a single array of bytes with the "Splash\0" at the start, then reference the required offset to get the image data.

In eepe, do you just look for the word Splash, or do you also check for the 128 and 64 as well? The word Splash appears elsewhere in the code, so if the 4.7.0 compiler puts the image elsewhere, (as the Arm compiler does), will you miss the actual image?

Mike.

[Zloyuzver]

In version er9x (r-766) and er9x (r-767) again the same problem with the change Splash Screen.

[MikeB]

The 4.7.0 compiler did move the Splash marker, try r768, I think I got it back to the right place.

Mike.

[Zloyuzver]

Thank you. Now everything is working correctly.