Notifications
Clear all

New Member - Currently trying to get my ESP32 CAM to work

38 Posts
6 Users
13 Likes
2,257 Views
Ron
 Ron
(@zander)
Illustrious Member
Joined: 3 years ago
Posts: 4805
 

@pete WiFi was originally invented by actress Hedy Lamarr. The IEEE 802.11 group codified WiFi as we know it today. Espressif and uBlox likely both pay royalties to someone for the WiFi concept or it may be now public domain. Yes, as I said, the RP2040 microcontroller invented by Raspberry Pi has been licensed to many other board builders, but as you point out mainly as microcontrollers, only Raspberry AFAIK uses the chip as a partner to a SOC on a microcomputer. Also, I have a board that has an Atmel MEGA328P as well as an Espressif 8266. Both those chips are logo'd so not clones, but the entire board is an Arduino (UNO form factor) + Espressif ESP8266 clone. Looks like an UNU, same barrel jack input  and programmed via USB, no FTDI (it's built in with the CH340G chip on board)

Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting


   
ReplyQuote
Ron
 Ron
(@zander)
Illustrious Member
Joined: 3 years ago
Posts: 4805
 

@davee Yes, it's confusing because the external power in the case of say an Arduino UNO is 9 volts typically, can even be a little higher and the ESP32-CAM is 5V even though it is internally 3.3V. The other confusion is the word Arduino. Even though the Arduino IDE handles ESP8266, ESP32, even RP2040 now, they are NOT boards made by/for Arduino Corp. they are a different company, Espressif and Raspberry Pi. I am sure we all do it, but we innately (with time and experience) know that an ESP32 is NOT an Arduino product even though the same code can be compiled for either board. Thank you for correcting my error, I do hate to make a mistake, but as of tomorrow I am 80yo and the brain is not what it used to be.

Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting


   
ReplyQuote
(@yurkshirelad)
Honorable Member
Joined: 2 years ago
Posts: 475
 

Happy birthday @zander!


   
ReplyQuote
Ron
 Ron
(@zander)
Illustrious Member
Joined: 3 years ago
Posts: 4805
 

@yurkshirelad Thank you!

Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting


   
ReplyQuote
(@maxli)
Trusted Member
Joined: 2 years ago
Posts: 37
 

Hello, this is my understanding hope to help you.

When calling a function, the original base address (EBP) of the stack is first placed on the stack to save the information of the previous task. The value of the top of the stack pointer is then assigned to the EBP, the top of the previous stack is used as the new base address (the bottom of the stack), and then the corresponding space is opened on this base address to be used as the stack of the called function. After the function returns, the previous ESP value can be taken from the EBP to restore the position before the function call at the top of the stack; and the previous EBP value can be ejected from the top of the restored stack, because this value is pressed into the stack one step before the function call. In this way, both EBP and ESP restore the position before the call, and the stack restores the state before the function call.


   
ReplyQuote
(@maxli)
Trusted Member
Joined: 2 years ago
Posts: 37
 

I think you can also choose TFT LCD. I used it before. It's really good.


   
ReplyQuote
Ron
 Ron
(@zander)
Illustrious Member
Joined: 3 years ago
Posts: 4805
 

@maxli I think you responded to the wrong post.

Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting


   
ReplyQuote
Ron
 Ron
(@zander)
Illustrious Member
Joined: 3 years ago
Posts: 4805
 

@maxli Again responding to ?

Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting


   
ReplyQuote
Page 3 / 3