MultiWii

Dilbert66

treym, looks like the latest version of the compiled release dfu is not saving settings. Keeps reverting back to default on reboot. I have not had a chance to look at the code so can't comment on what the issue is. I have not rebuilt my dev enviro so didnt recompile to try out locally. Just noting i...

Dilbert66

Nice work treym. A quad yoyo

Dilbert66

Does it actually download it but not work? or does it refuse to download it? Some of those stm32f103c8 do have 128k of flash even if they are listed as 64k from what I understand. edit: FYI, the later rev's of naze32's (not sure when the switch was), use an stm32f103CB which is a 128k device so has ...

Dilbert66

it's not the size of the hex that matters, it's how you use it

I use the same same setup with linux and my hex comes in at 222116 with GCC and arm embedded. It works fine. Hard to say why yours won't work. Are you compiling via Eclipse or are you using the makefile directly?

Dilbert66

Not to everyone. Hardware ports to other platforms being worked on. Timecop has other fish to fry..

Dilbert66

Far from it.

Dilbert66

Hmm, weird. Is it the old plastic (white) cap 5611 or the new metal ones? I've never used plastic, but out of all the ones I shipped with metal cap I never seen this bad prom CRC. Baro is the most expensive component on my boards, and while they're sometimes available cheap, I go for the "usua...

Dilbert66

Who gives a shit what the code looks like???? If it works... IT WORKS! Developers care. Shit code causes people to write more shit code. Having easy to understand and debug code, means that it will be sustainable and easy to add more beloved features. Having code that looks like speghetti and havin...

Dilbert66

Very good idea for those that can compile their own hex after making the necessary code changes to support the different mag but otherwise the default code will pick what it knows and will ignore the new one

Dilbert66

Geez... I really hate to see great minds disagree but such is the world of any dev project. Personally, I am not attached to any one project as my interests are quite varied. I'm not just flying these things. I like the coding aspect just as much and very interested in automation, GPS nav, telemetry...

Dilbert66

Good stuff Dominic! It's on my watch list

I'll be looking closely at your naze32pro branch as I have a shiny new one that I will be playing with soon. Just got to wait for my swd debug connector to arrive... I like your soft serial mods.

Dilbert66

What's the main issue you are finding with GPS on soft serial? Is the 19200 speed not adequate to keep up?

Dilbert66

IMG_20140525_093021.jpg I have a couple of these. Pretty cheap. m 64 pin variant. Gives better access to the third hardware serial port without sacrificing other pins. I still prefer the 48 pin footprint for compactness but for dev this is pretty cheap and works. Have gps, stlink/v2 debugging, gy-8...

Dilbert66

Which rev board are you guys running? Did you try the cli setting emf_avoidance which overlocks the naze32 to 84 mhz (assuming a 12mhz xtal for the rev5) set up for this reason . Older revs overclock to 80mhz I believe with an 8mhz xtal.

Dilbert66

I don't see any support for the spi sensors 6000, 5911, etc yet in that branch. Initial setup I assume.
Yea, another thread would be good. Prevent cluttering up the other threads.

Dilbert66

Just got it in the mail today. Time to play.

Dilbert66

Nice! Still waiting for mine. Did you use ff32mini spi drivers?

Dilbert66

e_lm_70 is correct, the 5883 can be disabled in firmware by turning off the 6050 i2c bypass in drv_6050.c here by removing the I2C_BYPASS_EN bit control and recompiling. I assume that Its not a cli control option cause I don't know anyone else that needs to do this on the fly so noone wanted to was...

Dilbert66

e_lm_70 is correct, the 5883 can be disabled in firmware by turning off the 6050 i2c bypass in drv_6050.c here by removing the I2C_BYPASS_EN bit control and recompiling. I assume that Its not a cli control option cause I don't know anyone else that needs to do this on the fly so noone wanted to wast...

Dilbert66

Most likely there is. You would have to do a comparison. This might be more noticeable if math operations were done. A better compiler will be able to optimize code to work for best speed and size. It's a compromise with GCC and most compilers I believe. You can compile for the smallest size, but th...

Dilbert66

Wiil do!

Dilbert66

Time to move to the stm32F303CCT6 ! Unfortunately, there are not too many of those uber cheap dev boards for that 48pin stm32 around like there are for the 103

Dilbert66

Liking it. Nice work

Dilbert66

The ms5611 in the gy86 module i have here has zero for those manufacturer bytes so its not always used

Dilbert66

Well, fucking lol. So random numbers in "some" BMP180s will succeed MS5611 CRC check. How freakin annoying. Perhaps just put the bmp check before the ms5611 detect and it should work. Of course, now we're depending on the bmp chip id to be meaningful. Is it the same chip id for the 180? S...

Dilbert66

What's with the signed values? Anyhow, after converting back to unsigned int and calculating the crc using the ms5611 algo, I get a calculated crc of "0x0c" which matches the word 7 lsb crc. So this would explain why it shows as a 5611. That would be a rare occurence if this is a fluke. Un...

Dilbert66

Still doesnt prove anything. bmp180 also stores co-efficients in prom. It just doesnt use a crc to validate them. All you are showing is that there is data at address 0xA0 in the "bmp180". Just post the values you get and I will calculate the crc and then we will know for sure. Make sure y...

Dilbert66

the values are 16 bit, you need to show all 8 to be able to calculate the crc from iit. The first one is normally (or can be) zero (manufacturer code).
You are treating them as 8 bit. I don't see why you say it is self evident? What you show doesnt prove anything.

Dilbert66

Just dump the 8 prom values and calculated crc with a debug print and see what you get.

Dilbert66

Very curious about that myself as the checksum code is a fairly accurate and a good test. There is even a check to ensure even with all prom at all zero's it wil be caught. It would be very strange indeed if random values would give a correct crc for the prom check.

Dilbert66

Well, e_lm_70, I think it's time you roll up your sleeves, hook up st-link with openocd or st-util and eclipse and trace the sensor init routine in the drv_bmp085.c code and compare outputs with other working code. Only way you'll know for sure where it fails. If you do find a flaw in the code , gre...

Dilbert66

Quite interesting though that you are having the same issue that I was having with the ms5611 baro with the 10dof module I had (mpu6050,5883 and 5611). Try doing what I said with the -O option and also try one other thing if that doesnt work. Change the i2c init speed from 400khz to 100khz in the dr...

Dilbert66

Don't be so quick to blame baseflight. If TC says it was tested and works then it does. You might also want to look at your compiler and compiler options. I had an issue with a sensor module and the problem was related to the compiler I was using with the -O0 flag which I use for debugging. Switchin...

Dilbert66

e_lm_70 wrote:I'm new in Naze32.

I did set up my Ubuntu for compile the Naze code.
Via SVN I got the revision 473.

SVN? That must be the old repository. The project moved to github a while ago. Here is the latest source:

https://github.com/multiwii/baseflight

Dilbert66

I get 216k with gcc and using -Os optimization and using the Launchpad toolchain. I couldnt' get CodeSourcery to work right. TC gets it at 169k with armcc.

armcc (Keil) is a commercial product and will indeed produce a much more optomized hex. GCC is for us cheap folks

Dilbert66

I agree. I always wondered what you used to compile since your hex was always smaller then a gcc optomized version. I believe I will switch.

Dilbert66

Hmm, weird. Is it the old plastic (white) cap 5611 or the new metal ones? I've never used plastic, but out of all the ones I shipped with metal cap I never seen this bad prom CRC. Baro is the most expensive component on my boards, and while they're sometimes available cheap, I go for the "usua...

Dilbert66

github with change control is the better way. Interested folks can even see what has changed from version to version normally. They can clone the project and be able to follow it's development and even contribute if they so desire and the project lead is open to it. The project would then be nourish...

Dilbert66

Hmm, weird. Is it the old plastic (white) cap 5611 or the new metal ones? I've never used plastic, but out of all the ones I shipped with metal cap I never seen this bad prom CRC. Baro is the most expensive component on my boards, and while they're sometimes available cheap, I go for the "usua...

Dilbert66

Thanks TC. I like the specs on it. I'll keep my eye out if you make more. Might be interested if the price is right. Porting baseflight to it should be fairly trivial . All the hard low level work has already been done by jihlean's focusflight port to your board.

Dilbert66

Off topic, are you planning on making any more of those stm32f303 boards ? m. Or a variant of the Rev5 board with the f303 (minus the usb chip since you have vcp). I like the fact that the 303's have a more flexible port remapping structure than the f101's giving better access to usart3 and other po...

Dilbert66

it's a newer metal one. I know the crc code is fine as I even tried the same values with the AN520 sample code and got the same results calculated crc=0, prom crc=8. Beats me. Well, you get what you pay for I guess. I was thinking it was a flaky i2c bus since I am using soldered on lengths of about ...

Dilbert66

I'm playing around with an STM32f103RBt6 breakout board and a GY-86 cheapie IMU unit from China. ACC, MAG and Gyro work fine but it was not picking up the ms5611 baro. A quick debug session showed that the chip was responding fine on i2c but was consistently failing the prom crc. Just to see what th...

Dilbert66

[list=][/list]Thats a good eclipse gdb setup. I was always a command line guy but have warmed up to eclipse in recent times. Not having frsky or graupner tx i cant really test the telemetry part but it sure adds versatility. I use 3dr radios for data. Can hott data streams be used for osd ? Too slow...

Dilbert66

What is to stop us from taking a page from his book and creating our own fork Nothing, and git and github encourages this. However, rather than just merging into a new codebase from baseflight why not contribute to baseflight? As a baseflight developer I'd be happier if we all worked together to im...

Search found 45 matches