Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Linux in embedded systems main appeal is time to market and ease of use. From a hardware stand point there is a decent amount of support in terms of kernel modules and device drivers. From a software perspective it has a large number of stuff such as filesystems and networking along with various...
So this is not really adding up anymore. C++ would not likely be the operating system and almost definitely not the boot-loader. Those are traditionally written in C or assembly at least on lower level devices. While in theory they can be written in C++, but that would be C more or less due the...
Thanks for answering those questions. My guess currently is this is an embedded OS style device, where the hard drive is a secondary data drive. Generally in those devices what you have is three main components for booting up: CPU, RAM, and a ROM. The ROM contains a boot loader that is stored...
So a few questions to help me understand.
1) There is a hard drive which runs some kind of file system?
2) The bin file is copied to the hard drive?
3) There is a flash chip also in the device?
4) The flash chip is what runs the device or boots it up?
5) Do you know what the console prints in...
There is a bus that is used for something reserved in hardware on the PI. However I am not sure which bus it was exactly. I know there is at least one free I2C bus that could be used. The kernel modules are generally implemented to take advantage of DMA and other features behind the scenes to...
The data is 8 bits but the address is 7 or 10 bits. The DS3231 uses 7 bit addressing.The read/write plus the 7 bit address is also 8 bits. So the address range would be 0x0 to 0x7F.
There is an address range check here...
I2C uses 7 bits or 10 bits for the address, however 7 bits is the more common way. The upper 7 bits are for the address and the lsb is for signaling read or write.
According to the data sheet the address is 0x68. So you should not be fine with the current setup. If I remember correctly some of...
This is somewhat of a generalization, as it can depend on the implementation/design.
Usually a reset is used to clear/reset the state/memory of the system to a predetermined value. Can be isolated or global.
Whereas an enable usually allows the system to suspend operation such that it...
You flipped the RX and TX? You are using the same baud rate? (Just basic questions for serial.)
The MAX232 is not the correct level converter. That is meant to convert TTL to RS232 voltages.
Does the SIM900A run at 3v?
On page 10 it talks about the speed of the clocks under Fmax. The frequency depends on temperature and voltage of the supply. So I would say that you can do 20MHz min on 5V at any temperature range. Now more than likely you could go much faster, but the datasheet only discusses 4.5 and 6V. My...
See this is the part that actually confuses me the most. I2C code is a fairly straight forward protocol and the hardware interface is fairly minimal and well documented. I am pretty sure that you could google it. Also microchip implements hardware routines for things like the I2C bus on most all...
This sounds like the behavior of RAM not EEPROM. I am also curious if the EEPROM is actually getting data. I know that there is some funny unlock sequence for it accept writes as mentioned earlier. However I am not sure why that would cause it to magically record and return the correct values...
I do not see a way. I checked the port pin descriptions where T2CKI is not mentioned in any of the ports. Timer 2 registers do not mention a clock source bit. Nor does the Timer 2 diagram mention a clock source other than Fosc/4.
It is possible it was copy paste or the are using counter in...
Well that is what I said, but I still say that it is possible. memcpy for example is going to be really easy to spot on just about any compiler or architecture. (Not exactly a practical example seeing how simple it is.) Plus you could just brute force with trial and error on several compilers...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
