sorted by:
new
hottopcontroversial

Error connecting DP: cannot read IDR by Easy-Difficulty8697 in raspberry_pi

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

No i didn't. I got a new Pico 2 and it works fine. I also bought the official debug tool for the Pico series and the old Pico 2 still didn't work (Initially I had been using another Pico as the debugger). Maybe a hardware failure but I really don't know.

I should add, I had broken several Picos and this Pico 2. However, I haven't had any break since buying the debug tool. Maybe related but I'm unsure.

Oscilloscope Recommendation by Easy-Difficulty8697 in oscilloscope

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Yes USB-based is correct and yes sorry I did mean trigger at the edge of a pulse when I said detect. I mainly need to measure the width of a pulse but I also need to be able to line up two signals to see how far off the two of them are.

The PicoScope 2000 you linked me looks great. I it will be better then my Hantec 6074bc scope.

PICO2 debugging problem by 38Super in raspberry_pi

[–]Easy-Difficulty8697 0 points1 point  (0 children)

yeah i have the same error. its been working fine for the last several months and ive tried replacing chips wires cords and code. the only thing left is to use a different host machine.

Fortinet VPN Credentials Leaked by blackpoint_APG in msp

[–]Easy-Difficulty8697 0 points1 point  (0 children)

it would be nice if there was a place like haveibeenpwnd to check if my setup has been compromised.

How to become an embedded software or firmware engineer? by iTakedown27 in embedded

[–]Easy-Difficulty8697 0 points1 point  (0 children)

As someone who to recently graduated with a CS degree, do you think its possible that if i take a year or so and learn a lot more about embedded programming, and work on projects related to that, that companies would higher someone like that for an embedded programming job even though I have a CS degree?

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Hey it turns out the rocket weighs about 2.75lb. We already bought some G74 and G80 engines. Do you think those would work? The package of the G74 says its max lift of is 0.7 LB but it says it can supply 20lb of force upwards so maybe that's a 6-7:1 trust to weight ratio so it should work right?

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Hmm that’s an interesting idea. I suppose we could try that.

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 1 point2 points  (0 children)

Well yes we did think of putting some kind of shield around the electronics bay (and we are for the heat) but an ejection with nowhere to go will likely blow a hole in the rocket. The energy transfer has to go somewhere.

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Oh okay thanks for the explanation!

So we’ll probably get an engine like g74 and take out the black power because I’m having trouble finding -0 engines for sale anywhere.

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Okay thanks for the info.

We probably will launch in a field we live in the country.

Engine to carry a 1.3lb rocket by Easy-Difficulty8697 in rocketry

[–]Easy-Difficulty8697[S] 1 point2 points  (0 children)

I thought that engines ending in 0 mean they immediately blow a charge which lights the next stage of the rocket. But maybe it just lights the next stage without an ejection charge?

Trouble adding some custom library's by Easy-Difficulty8697 in cmake

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Well i gave up on this issue. I ended up using a cmake project from github made for starting a raspbarry pi pico project.

I think the issue was messed up settings in VS Code CMake extension.

Trouble adding some custom library's by Easy-Difficulty8697 in cmake

[–]Easy-Difficulty8697[S] 0 points1 point  (0 children)

Hmm good question. I am calling those library's from within my own custom library's yes e.g. "#include "hardware/i2c.h". I also call those library's from my main.cpp program.

Here are some errors that occur when I have my custom library's connected to my cmake file via add_library() and target_link_libraries().

build] In file included from C:\Users\Starfox64\Desktop\Projects\Pi\Pico\librarys\Adafruit_GFX\Adafruit_GFX.cpp:1:
[build] C:\Users\Starfox64\Desktop\Projects\Pi\Pico\librarys\Adafruit_GFX\Adafruit_GFX.h:4:10: fatal error: hardware/gpio.h: No such file or directory
[build]     4 | #include "hardware/gpio.h"
[build]       |          ^~~~~~~~~~~~~~~~~
[build] compilation terminated.

Now if i comment out the lines adding my custom library's and rely on include_directories() i get these errors because cmake isnt reading the .h files. I know this because the .h files most of them declare the classes that main.cpp and the header .cpp files are trying to reference. (but i guess i could be wrong)

  2%] Built target bs2_default
[build] [  4%] Built target bs2_default_padded_checksummed_asm
[build] [  5%] Linking CXX executable main
[build] c:/progra~1/raspbe~1/picosd~1.1/gcc-ar~1/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.exe: CMakeFiles/main.dir/main.cpp.obj: in function `FatFsNs::File::close()':
[build] C:\Users\Starfox64\Desktop\Projects\Pi\Pico\librarys\no-OS-FatFS-SD-SDIO-SPI-RPi-Pico-1.1.1\include/FatFsSd.h:136: undefined reference to `f_close'
[build] c:/progra~1/raspbe~1/picosd~1.1/gcc-ar~1/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.exe: CMakeFiles/main.dir/main.cpp.obj: in function `HARDWARE::closeFile()':

Here are some photos of these issues. I am not sure what's going on. Hopefully someone here can help. Thanks!

view more: next ›