Build messages

Start
Prev
1
Next
End

blackmoon
Topic Author
Offline

18 Nov 2013 12:24 - 18 Nov 2013 14:38 #15676 by blackmoon

Build messages was created by blackmoon

I'm using sbstnp's VM to build for devo7e, I patched the 3.1 trunk to have 1-3way switch enabled.

In the build log file I have this :

...
 + Compiling 'protocol/v202_nrf24l01.c' as module
 + Building 'objs/devo7e/v202_nrf24l01.bin'
Building v202 module
Found 12 ranges
Found 16 ranges
Found 1 ranges
Found 3 ranges
 + Copying template files for devo7e
 + Checking string list length for devo7e
...

If "rm -r ~/dev/deviation3.1" then run setup again to start from scratch, then patch the source tree with the HiSky protocol patch, I get the same messages but only for the HiSky module :

...
 + Compiling 'protocol/v202_nrf24l01.c' as module
 + Building 'objs/devo7e/v202_nrf24l01.bin'
Building v202 module
 + Compiling 'protocol/hisky_nrf24l01.c' as module
 + Building 'objs/devo7e/hisky_nrf24l01.bin'
Building HiSky module
Found 12 ranges
Found 16 ranges
Found 1 ranges
Found 3 ranges
 + Copying template files for devo7e
 + Checking string list length for devo7e
...

If I compile either sources a second time after a "deviation cleanup devo7e", the range messages don't show...

EDIT: this is normal behavior, I think, just saw that .elf files for modules aren't cleaned by a "deviation cleanup".

...
Building skyartec module
 + Compiling 'protocol/v202_nrf24l01.c' as module
 + Building 'objs/devo7e/v202_nrf24l01.bin'
Building v202 module
 + Copying template files for devo7e
 + Checking string list length for devo7e
...

...
 + Compiling 'protocol/v202_nrf24l01.c' as module
 + Building 'objs/devo7e/v202_nrf24l01.bin'
Building v202 module
 + Compiling 'protocol/hisky_nrf24l01.c' as module
 + Building 'objs/devo7e/hisky_nrf24l01.bin'
Building HiSky module
 + Copying template files for devo7e
 + Checking string list length for devo7e
...

Anyway, what do the range messages mean ?

Is it normal that they don't show, for both v202 and HiSky, if the tree is patched with the HiSky protocol ?

I remember when I done a build with 2 2-way switches + HiSky, MassiveOverkill tested it and said that the V202 protocol was broken...

Could it be those range messages not showing for V202, when building the firmware with the HiSky module ?

However, I end up with a build done without errors.

Last edit: 18 Nov 2013 14:38 by blackmoon.

Please Log in or Create an account to join the conversation.

victzh
Offline

18 Nov 2013 14:16 #15678 by victzh

Replied by victzh on topic Build messages

I doubt that this is these "ranges" to blame. I need to look at it with just Hisky and V202 - they both use nRF24L01 and can interfere each other.

I also don't know what ranges are, but suspect that's how module system manifest itself in the build. The modules must be mapped onto the same place and may be some script is searching for link layout for this.

Please Log in or Create an account to join the conversation.

blackmoon
Topic Author
Offline

18 Nov 2013 14:40 - 18 Nov 2013 14:41 #15679 by blackmoon

Replied by blackmoon on topic Build messages

I didn't test my build, because I'm waiting for the nRF module from Banggood.

But even then I can't test for V202 as I don't have any.

If it works for HiSky with the 3-way switch, I'll be happy...

Hopping that it won't interfere with another protocol to.

I was just intrigued by the range messages.

Last edit: 18 Nov 2013 14:41 by blackmoon.

Please Log in or Create an account to join the conversation.

rbe2012
Offline
So much to do, so little time...

18 Nov 2013 14:41 #15680 by rbe2012

Replied by rbe2012 on topic Build messages

Those messages are normal. They appear it the filesystem has to be built new and the font files do not exist (in media folder, *.fon).

Please Log in or Create an account to join the conversation.

blackmoon
Topic Author
Offline

18 Nov 2013 14:44 #15681 by blackmoon

Replied by blackmoon on topic Build messages

ok then, it has nothing to do with the functionality of the module built, and should only appear once for all modules in the filesystem.

So Victor it's up to you to test why the HiSky protocol interferes with the V202.

Sorry I know you have a lot on your plate right now

.

Rbe, thank you for the explanation.

Please Log in or Create an account to join the conversation.

Start
Prev
1
Next
End

Time to create page: 0.031 seconds

Re-enable mobile display