SmartXX LT OPX modchip RGB LED bug?

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
tinux Offline
Junior Member
Posts: 18
Joined: Sep 2007
Reputation: 0
Location: Netherlands
Question  SmartXX LT OPX modchip RGB LED bug?
Post: #1
Hi,

I have a SmartXX LT OPX and soldered some leds on it.

Now the problem I'm having, is that I can only control the Red channel with the LCD backlight value, and the Green and Blue channels with the pwmcontrol (via python)

Sidenote: A solution I wouldn't mind to use is something like "lcd.backlight" in the built-in commands, except that it isn't implemented.

So I looked into the code and saw
Code:
// utils\LED.h
#define SMARTXX_PWD_RED    0xf70c   //PWM1: SmartXX V3 port for RGB red output
#define SMARTXX_PWD_GREEN  0xf70d   //PWM2: SmartXX V3 port for RGB green output
#define SMARTXX_PWD_BLUE   0xf70e   //PWM3: SmartXX V3 port for RGB blue output

and furthermore:
Code:
// lib\smartXX\smartxxlcd.cpp
#define DISP_O_LIGHT              0xF701        // Display Port brightness control

And when I check this with the SmartXX LT OPX 'datasheet', it shows me:
Code:
F701h (write) PWM1 out (brightness control)
..
F70Ch (write) PWM2 out (brightness control)
F70Dh (write) PWM2 out (brightness control)
(..end of table)

0xf70e doesn't exist!
Also SMARTXX_PWD_RED actually is Green on the pinout.
and likewise for SMARTXX_PWD_GREEN which is my 'blue'


So is this a bug / incompatibility?
I think there should be a check for the SmartXX version or something inside the LED.cpp or via a smartXXled.cpp subclass.

Would be nice to see this working correctly, but unfortunately, I do not have the right equipment/knowledge to compile XBMC myself atm.

cheers,

tinux

using an XBMC rev30380 with updated LCD code
find quote
jmarshall Offline
Team-XBMC Developer
Posts: 26,181
Joined: Oct 2003
Reputation: 176
Post: #2
Hi there,

You may well be correct. Unfortunately, I (and I suspect most devs) don't have said modchip to experiment with.

I suggest the best course of action would be to fix it yourself. Wink

The second best course of action would be to file a bug report on sourceforge with this information, and assign it to GeminiServer who did this bit of code.

Cheers,
Jonathan

Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


[Image: badge.gif]
find quote
tinux Offline
Junior Member
Posts: 18
Joined: Sep 2007
Reputation: 0
Location: Netherlands
Post: #3
Finally I've managed to compile xbmc, and therefore test if changing the addresses would work.

To be honest, I think the impact of changing it for me would be too big, so I made a bug report.

[offtopic]
Also, the wiki list of built in functions is outdated on the pwmcontrol part:
it should say XBMC.system.pwmcontrol(#ColorA,#ColorB,#WA,#WB,action,xTime)
where #WA and #WB is a value between #00 and #ff for the white status led in (allthough it can only be on or off)

I couldn't edit the wiki though, and I'm not sure where to post this
[/offtopic]

using an XBMC rev30380 with updated LCD code
find quote
GeminiServer Offline
Senior Member
Posts: 174
Joined: Oct 2003
Reputation: 0
Post: #4
OPX Support is added, use the latest svn and check again.

Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


[Image: badge.gif]
find quote