Wednesday, October 26, 2005
Tasks for the week
So... to get started here are some things on my plate, some of which are customer-driven and others which aren't.
- GHS temp license no longer working. It was supposed to be 180 days, but it stopped working after less than 30. Opened issue for tracking by GHS.
- VPN: now that I've got access I need to get remote compilers working with Clearcase etc.
- Targets: after some LAN reconfiguring, my access to the MBX860 was messed up. Got this fixed the other day. (Note to self : NEVER try to use 192.168.x.x for target!!!) I have two other targets that I'm slowly working on getting going, but other tasks seem to get in the way. One is an OMAP OSK5912 board and the other is an EST8260. I'm hoping to get 5.1 on the OMAP and 4.6 on the 8260.
- iSystem and other misc debugging items: these are languishing here but I do want to get freeze-mode working at some point with either MULTI or GDB. Preferably both.
- received 4.6.1 source in the mail this week. Which is great, except I don't have 4.6.1 release. Which I need to get, I think!
- Other components which I need to get more familiar with like POLO, SNMP etc.
*** Now for some open customer issues. ***
- Illuminator customer using osepmd.jar with fixes. The updated zipped /bin/jre was sent to them this week and I'm waiting to hear if this closes their issue.
- Diab 5.0a compiler issues: working this through with customer still, trying to get them going on the 4.x versions that we know to be working. Customer has install issues now with diab software that they're trying to get worked out.
- GHS linker warning ose_confd.o: no update on this, need to find workaround. My license issue needs to get fixed and/or VPN access to compilers is needed.
- sfk-linux and Illuminator: works for me, but on the site it doesn't see the target app, which is a consultant product. FAE will be onsite soon to work with it more. Need something to monitor the UDP ports for Illuminator to find out why it can't see the app. Tried udplisten but this doesn't work in the context of this sfk, which totally locks up the port (udplisten returns bind() error). We also received some process logs from the customer app, one of which shows very interesting data that looks like a tick() calling process being starved.
- 5.1 BSP for 5912 : changing clock speed appears to have no effect. Paul N. is working very hard on this and explained to customer the impact of fixing it. Customer is okay with this so Paul will send the fixes to them. As far as sourcing, no idea - need to follow up on this so probably I will write a case to get it sourced.
*** Random thoughts ***
Sent some feedback to mgmt about defining End Of Life process. It's good that they're thinking about this, even though it's a painful subject for customers and difficult for the field people sometimes to talk about it with them. I agree though that something is needed - if anything it helps clarify what can be offered for older releases. But if we are not very aggressive about forcing upgrades on the base (i.e. Sun is quite aggressive about this and EOLs their old java stuff as soon as a new release is out), the product retirement process can really drag on for a long time.
- GHS temp license no longer working. It was supposed to be 180 days, but it stopped working after less than 30. Opened issue for tracking by GHS.
- VPN: now that I've got access I need to get remote compilers working with Clearcase etc.
- Targets: after some LAN reconfiguring, my access to the MBX860 was messed up. Got this fixed the other day. (Note to self : NEVER try to use 192.168.x.x for target!!!) I have two other targets that I'm slowly working on getting going, but other tasks seem to get in the way. One is an OMAP OSK5912 board and the other is an EST8260. I'm hoping to get 5.1 on the OMAP and 4.6 on the 8260.
- iSystem and other misc debugging items: these are languishing here but I do want to get freeze-mode working at some point with either MULTI or GDB. Preferably both.
- received 4.6.1 source in the mail this week. Which is great, except I don't have 4.6.1 release. Which I need to get, I think!
- Other components which I need to get more familiar with like POLO, SNMP etc.
*** Now for some open customer issues. ***
- Illuminator customer using osepmd.jar with fixes. The updated zipped /bin/jre was sent to them this week and I'm waiting to hear if this closes their issue.
- Diab 5.0a compiler issues: working this through with customer still, trying to get them going on the 4.x versions that we know to be working. Customer has install issues now with diab software that they're trying to get worked out.
- GHS linker warning ose_confd.o: no update on this, need to find workaround. My license issue needs to get fixed and/or VPN access to compilers is needed.
- sfk-linux and Illuminator: works for me, but on the site it doesn't see the target app, which is a consultant product. FAE will be onsite soon to work with it more. Need something to monitor the UDP ports for Illuminator to find out why it can't see the app. Tried udplisten but this doesn't work in the context of this sfk, which totally locks up the port (udplisten returns bind() error). We also received some process logs from the customer app, one of which shows very interesting data that looks like a tick() calling process being starved.
- 5.1 BSP for 5912 : changing clock speed appears to have no effect. Paul N. is working very hard on this and explained to customer the impact of fixing it. Customer is okay with this so Paul will send the fixes to them. As far as sourcing, no idea - need to follow up on this so probably I will write a case to get it sourced.
*** Random thoughts ***
Sent some feedback to mgmt about defining End Of Life process. It's good that they're thinking about this, even though it's a painful subject for customers and difficult for the field people sometimes to talk about it with them. I agree though that something is needed - if anything it helps clarify what can be offered for older releases. But if we are not very aggressive about forcing upgrades on the base (i.e. Sun is quite aggressive about this and EOLs their old java stuff as soon as a new release is out), the product retirement process can really drag on for a long time.
free invisible web counter
