Developing a universal module

More
13 Apr 2014 23:36 #22389 by PhracturedBlue
Replied by PhracturedBlue on topic Developing a universal module
that hardware.ini should behave no differently than the default. It should work just fine. If not, it implies a wrong connection somewhere.

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

More
14 Apr 2014 08:19 #22394 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
Ok I did some test :

i) Devo 10 standalone with last NB : OK

ii) Devo 10 + a NRF24L01+PA standalone (using my soldering job on debug port and CYRF6936) : OK



iii) I checked all connectivity of the multi-module and for me it's ok ...

Here are some photos

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

More
14 Apr 2014 08:19 - 14 Apr 2014 19:13 #22395 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
Ok I did some tests :

i) Devo 10 standalone with last NB : OK

ii) Devo 10 + a NRF24L01+PA standalone (using my soldering job on debug port and CYRF6936) : OK (flew a V272 quad using V2x2)



iii) I checked all connectivity of the multi-module and for me it's ok ...

Here are some photos











EDIT :

Can I install one module by one module on the multi-module for testing?

In the worst case, I want to unsolder the CC2500 and the nRF24L01 in order to test first the A7105-500.
Attachments:
Last edit: 14 Apr 2014 19:13 by SeByDocKy.

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

More
16 Apr 2014 21:54 #22485 by blackmoon
Replied by blackmoon on topic Developing a universal module
I also have the CYRF module missing warning. I have DEvo7e internal Cyrf, NRF + skyartec + 7105 on the MM.

Unfortunately, I also have issues with he NRF, I have to power cycle the TX for it to initialize, I think (humming) and it doesn't bind with my Hisky birds. Only the skyartec and 7105 bind and work.

I tried all the latest nightlies,avr.hex V3, no joy... every time cyrf missing and no Hisky connection. The cyrf is missing even if I un-comment the "enable-cyrf6936 = B12"

My HW.ini
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
enable-a7105=S1
has_pa-a7105=1
enable-cc2500=S3
has_pa-cc2500=1
enable-nrf24l01=S402
has_pa-nrf24l01=1
enable-multimod=A13

I tested each module separately all are working ok, if no MM in place the CYRF is detected and works.

For the time being I took off the MM and re-installed the Skyartec and NRF modules (working ok), weather is good and I wanna fly :D

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

More
17 Apr 2014 03:25 - 17 Apr 2014 03:27 #22496 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module

blackmoon wrote: I also have the CYRF module missing warning. I have DEvo7e internal Cyrf, NRF + skyartec + 7105 on the MM.

Unfortunately, I also have issues with he NRF, I have to power cycle the TX for it to initialize, I think (humming) and it doesn't bind with my Hisky birds. Only the skyartec and 7105 bind and work.

I tried all the latest nightlies,avr.hex V3, no joy... every time cyrf missing and no Hisky connection. The cyrf is missing even if I un-comment the "enable-cyrf6936 = B12"

My HW.ini

;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
enable-a7105=S1
has_pa-a7105=1
enable-cc2500=S3
has_pa-cc2500=1
enable-nrf24l01=S402
has_pa-nrf24l01=1
enable-multimod=A13

I tested each module separately all are working ok, if no MM in place the CYRF is detected and works.

For the time being I took off the MM and re-installed the Skyartec and NRF modules (working ok), weather is good and I wanna fly :D



Interesting ... finally more or less the same symptoms that mine.
Did you try to install only one module in the MM and test it indivusually ?

Edit :

I don't have :

enable-a7105=S1
has_pa-a7105=1
enable-cc2500=S3
has_pa-cc2500=1
enable-nrf24l01=S402
has_pa-nrf24l01=1


in my HW.ini, just the enable-multimod=A13. I don't know if it's important or not
Last edit: 17 Apr 2014 03:27 by SeByDocKy.

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

More
17 Apr 2014 16:08 - 17 Apr 2014 16:13 #22508 by blackmoon
Replied by blackmoon on topic Developing a universal module
I don't know if it's important with the latest avr.hex rev 3 and the latest nightlies, and if enable-multimod=A13 is enough.

Hope PB will chime in.

Anyway shoving three modules into a 7E is a little nightmare, I think this is more targeted to 8/10/12. But it would be cool if it worked with the 7E.

I'll maybe order a second 7E to convert to MM when it works reliably, I already soldered/un-soldered to much on this one, I fear the pads won't stay next time...

Edit: I didn't try with one module hooked at a time onto the MM, all "single" module tests where directly soldered to the pads of the 7E motherboard.
Last edit: 17 Apr 2014 16:13 by blackmoon.

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

More
17 Apr 2014 17:35 #22510 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module

blackmoon wrote: I don't know if it's important with the latest avr.hex rev 3 and the latest nightlies, and if enable-multimod=A13 is enough.

Hope PB will chime in.

Anyway shoving three modules into a 7E is a little nightmare, I think this is more targeted to 8/10/12. But it would be cool if it worked with the 7E.

I'll maybe order a second 7E to convert to MM when it works reliably, I already soldered/un-soldered to much on this one, I fear the pads won't stay next time...

Edit: I didn't try with one module hooked at a time onto the MM, all "single" module tests where directly soldered to the pads of the 7E motherboard.


Tmr, I will unsolder the 3 chips and test MM one module by one module in my devo 10. I will also make a second MM to try to insert in my devo 7E

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

More
17 Apr 2014 18:31 #22513 by PhracturedBlue
Replied by PhracturedBlue on topic Developing a universal module
To clarify:
If you enable:
enable-multimod=A13
Then the CYRF module stops being detected. Did I get that right?
It is odd, as I have this installed in my Devo7e without this issue.
I'm going to try removing the check to see if the module is functional but just providing the expected feedback. I'll let you know when I have something ready to test.

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

More
17 Apr 2014 18:50 #22516 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module

PhracturedBlue wrote: To clarify:
If you enable:

enable-multimod=A13
Then the CYRF module stops being detected. Did I get that right?
It is odd, as I have this installed in my Devo7e without this issue.
I'm going to try removing the check to see if the module is functional but just providing the expected feedback. I'll let you know when I have something ready to test.


Well for me, I think I have two problems :

i) "Missing CYRF6936" message at startup
ii) Rebooting after (I guess due to bad soldering, I hope to solve tmr)

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

More
17 Apr 2014 19:41 #22520 by blackmoon
Replied by blackmoon on topic Developing a universal module
Yes if I have enable-multimod=A13 no more Cyrf detection.

But in my case I just dismiss it with the ok button and the tx boots with no others issues. Then just the Nrf not binding at all, the other two modules work fine.

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

More
17 Apr 2014 20:00 #22522 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module

blackmoon wrote: Yes if I have enable-multimod=A13 no more Cyrf detection.

But in my case I just dismiss it with the ok button and the tx boots with no others issues. Then just the Nrf not binding at all, the other two modules work fine.


So it clearly indicate that I have a problem with my MM. Hope to find tmr (I need some unsoldering pump)

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

More
17 Apr 2014 20:12 #22523 by blackmoon
Replied by blackmoon on topic Developing a universal module
Don't use a pump, it's a lot easier with solder wick. Since I bought some at DX the pump is collecting dust :)

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

More
17 Apr 2014 20:54 #22525 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module

blackmoon wrote: Don't use a pump, it's a lot easier with solder wick. Since I bought some at DX the pump is collecting dust :)


Well my solder wick is not really efficient. In fact, I will ask to a technician in my job (in the CMS dept) to do it :).

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

More
17 Apr 2014 21:39 #22527 by anarchy
Replied by anarchy on topic Developing a universal module
I have luck when I coat the wick in flux a little then use it it really soaks up the solder

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

More
18 Apr 2014 22:12 #22559 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
I desoldering both the CC2500 and the nRF24L01 for the MM, only the A7105-500 is remaining. Now I don't have any msg "missing .... protocol" but unfortunatly, I got a * front the FlySky, husband protocols for example :(.

I have only the enable-multimod=A13 in my HW.ini (I did a test enabling A7105 with S21 and I got the msg : "missing A7105 protocol"....

I checked all my soldering job from debug port + CYRF to the A7105-500 of the MM. Everything is in direct contact except CSN and MISO which can be found on the ATTINY. It seems that the ATTINY don't reroute the CSN and MISO to the A7105-500. Maybe I should check connectivity with my devo 10 powered on ?

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

More
19 Apr 2014 07:12 #22565 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
Did new tests .... I am becoming crazy

I tried to flash the hex with the dfu and I got "•ERR: No switch found". According to documentation, it means the AVR didn't initialize. I checked all the 7 connextions from sources (debug port + CYRF pins) to destinations (AVR pins of the MM) and contacts are OK.....

I am becoming crazy ....

In the hardware.ini got enable-multimod=A13 (I did a test enabling A7105 with S1 and no changes)

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

More
20 Apr 2014 10:33 - 20 Apr 2014 13:48 #22597 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
I unsoldered all module now .... and restarted flashing with avrdude. I am using the ATtiny 44A-PU... For me flashing seems to be ok. Here is the log
D:\Utilisateurs\SeBy\perso\Telecommande\multimodule>
D:\Utilisateurs\SeBy\perso\Telecommande\multimodule>avrdude -p t44 -c usbasp -e
-U flash:w:avr.hex

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.03s

avrdude: Device signature = 0x1e9207
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: reading input file "avr.hex"
avrdude: input file avr.hex auto detected as Intel Hex
avrdude: writing flash (338 bytes):

Writing | ################################################## | 100% 0.22s

avrdude: 338 bytes of flash written
avrdude: verifying flash memory against avr.hex:
avrdude: load data flash data from input file avr.hex:
avrdude: input file avr.hex auto detected as Intel Hex
avrdude: input file avr.hex contains 338 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.16s

avrdude: verifying ...
avrdude: 338 bytes of flash verified

avrdude: safemode: Fuses OK (E:FF, H:DF, L:E2)

avrdude done.  Thank you.

D:\Utilisateurs\SeBy\perso\Telecommande\multimodule>avrdude -p t44 -c usbasp -U
lfuse:w:0xe2:m -U hfuse:w:0xdf:m -U efuse:w:0xff:m

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.03s

avrdude: Device signature = 0x1e9207
avrdude: reading input file "0xe2"
avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0xe2:
avrdude: load data lfuse data from input file 0xe2:
avrdude: input file 0xe2 contains 1 bytes
avrdude: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of lfuse verified
avrdude: reading input file "0xdf"
avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xdf:
avrdude: load data hfuse data from input file 0xdf:
avrdude: input file 0xdf contains 1 bytes
avrdude: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.01s

avrdude: verifying ...
avrdude: 1 bytes of hfuse verified
avrdude: reading input file "0xff"
avrdude: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0xff:
avrdude: load data efuse data from input file 0xff:
avrdude: input file 0xff contains 1 bytes
avrdude: reading on-chip efuse data:

Reading | ################################################## | 100% -0.00s

avrdude: verifying ...
avrdude: 1 bytes of efuse verified

avrdude: safemode: Fuses OK (E:FF, H:DF, L:E2)

avrdude done.  Thank you.


EDIT : I tried to flash with devo10 and it doesn't work ... so for me... I guess there is a problem with .dfu to recognize the ATtiny44A-PU. I will receive some ATtiny22A, I will be able to confirm or not this problem
Last edit: 20 Apr 2014 13:48 by SeByDocKy.

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

More
20 Apr 2014 14:54 #22598 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
Maybe for the ATtiny44A, the L,H and E values are different ?

www.engbedded.com/fusecalc

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

More
20 Apr 2014 15:58 - 20 Apr 2014 16:41 #22599 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
Now I am wondering if I did the right wiring on my devo10

I used pins 4, 8, 10 of CYRF6936-DEVO for CSN, MOSI, MISO respectively and used NRESET, TMS, GND and VCC of the debug port (see photo)



According to wiki, I read :

CYRF6936-DEVO 1(5V) 5 3 8 10 2 Connect 9->5

Do I need to connect also the 5V from CYRF6936-DEVO to the P1 of MM ?. Do I need to instal a wire from 9->5 ?

EDIT : Maybe I found : "If the 'Universal Module' is being installed, 'CSN' should connect to the 'TMS' pin, and 'RESET' should connect to the 'TCK' pin" ....

I think, I stupidely connected RESET of P1 to NRESET of 'CONN5' header instead of TCK ...
Attachments:
Last edit: 20 Apr 2014 16:41 by SeByDocKy.

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

More
20 Apr 2014 19:48 #22608 by SeByDocKy
Replied by SeByDocKy on topic Developing a universal module
EUREKA ....

Stupidely connnected P1-RESET to NREST-CYRF-DEVO instead of TCK-CYRF-DEVO. Now it's flashing well with the devo :). I will reinstall module now one by one :)

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

Time to create page: 0.189 seconds
Powered by Kunena Forum