GetSet issue with vector length - Processors forum - Processors

0 Alan DeMars over 12 years ago

TI__Mastermind 30830 points

Hello,

Can you share your package.xdc, module.xdc, and module.xs files so I can have a look around?

I'll be checking for typos mostly.

Alan

0 Nick Borton over 12 years ago in reply to Alan DeMars

Genius 3595 points

I added a tar file under my user location.

0 Nick Borton over 12 years ago in reply to Nick Borton

Genius 3595 points

I implemented another length setter on a third module which is not working either. When I enable the debug flag in GetSet, the setter for length only has debug output output for the one module. the other two show nothing. And then the property which is printed is -1, not length

*** maybe setting Clocking/PostCallbackVector.-1 to 5, old value is 4
*** setting Clocking/PostCallbackVector.-1 to 5 (was: 4)

I attempted to use -1 instead of length in the modules where the setter is not working, and I get a different error:

js: "/BoardUtils/EthInit.xs", line 74: can't init xdc.services.intern.xsr.Value$Arr@1697b67::BoardUtils.EthInit/EthHwResetPins.-1

0 Alan DeMars over 12 years ago in reply to Nick Borton

TI__Mastermind 30830 points

I'd like to see the Mod.xdc and Mod.xs files of the module who's GetSet behavior is as you expected. And I'd like to see the .cfg files you're using to verify the behavior.

Alan

0 Alan DeMars over 12 years ago in reply to Alan DeMars

TI__Mastermind 30830 points

Try configuring the setters in module$meta$init().

module$meta$init() is invoked BEFORE the remainder of the .cfg script is parsed.

module$use() is invoked AFTER the .cfg file is parsed.

I'm thinking that the setters aren't installed until after the user's script is parsed. Too late to cause them to be invoked by user changes within the config script.

Alan

0 Nick Borton over 12 years ago in reply to Alan DeMars

Genius 3595 points

Adding them in module$meta$init worked.

Thanks for your help!