I'm trying to debug a program that uses SPI, using the uVision simulator. (uVision V188.8.131.52)
According to the data sheet, the MODF Mode Fault appears when "when a master mode collision is detected (NSS is low, MSTEN = 1, and NSSMD[1:0] = 01)."
I have the SPI configured for 4-wire master mode, MSTEN = 1 and NSSMD = 11. As soon as I set NSSMD0 = 0 to drop the slave-select line, the simulator throws a MODF fault. Does the simulator have its logic for NSSMD1 and NSSMD0 reversed? The software seems to work on the actual hardware without a problem.
I am developping a prototype of PCB that includes a 8051 as MCU. The board has just been made and I soldered only a few things, enough to be able to pull 4 signals out of the board:
As I read the doc about the 8051 (C8051F996), I found that only these fours signals are enough to flash the memory of the micro controller. Yet, when using the toolstick bellow I cannot get to flash anything inside the MCU. I am using Simplicity Studio and the following toolstick:
Note that when there is only a 8051 inside the toolstick (as in the picture) the flashing process works fine. When I take it out, and pull the 4 required signals to connect them to my board I get "[ERROR: Not connected to target.]".
I also tried the following with two sticks connected pin to pin (still 5, 6, 9, 10) and I managed to flash the 8051 on the left:
So it seems 4 wires are enough and something may be missing else where. Does anyone has any clue?
I must say that in my prototype board which I have no picture of, there is nothing but a 8051 so far, no capacitor, no resistor, nothing, VCC GND C2D C2CK go straight in it.
Thanks in advance for your tips
I am working on 8 bit MCU Evaluation board. Whenever I am going to debug my source code then its showing "CPU core could not start". Please let me know if any solution on this.
What is the minimum and maximum current that can be applied to an analog input destined for the ADC?
I have some passive input conditioning circuitry that may reduce the curent to an unacceptably low level. There isn't much said about input pin current requirements in the data sheet.
My chip is C8051F320.
I use PCA to measure frequency (15K~5K) and send to PC by USB as 1K speed.
I use interrupt as follow:
3.Timer0 as basetime for PCA
4.Timer1 as 1K to send data to PC
if PCA>USB windows can't find the chip.
if PCA<USB when USB working PCA will timeout then get wrong data.
Hello everyone, I need your valuable ideas ..
We create the usb keyboard based your mouse example with 8051f320. It works with some laptops but with some does not.
I do not understand the real problem. When I check with usb tool when problem happen it says string descriptors are not available(you can find it in the attachment). But sometimes as I said it works perfectly.
I will share the whole code. Can you check it ?
The EFM8SB1-RM.pdf the use of the lock byte but it contadicts the FLASH_PageErase() software
* @fn FLASH_PageErase * * @brief * This routine erases the flash page containing the linear flash address * <addr>. Note that the page of flash page containing the Lock Byte cannot be * erased if the Lock Byte is set. * * @param addr - address of any byte in the page to erase * valid range is from 0x0000 to 0x1FFF for 8 kB devices * valid range is from 0x0000 to 0x0FFF for 4 kB devices * valid range is from 0x0000 to 0x07FF for 2 kB devices * * @return void
Hi, I'm a beginner trying to connect a UB1 microcontroller to a TI drv8830 motor driver via I2C using the SMB bis on UB1. I'm using the starter kit example code Master SMB BUS and code from an141.pdf.
Where are global variable headers like SMB_DATA_OUT and TARGET initially defined? I can't find where they are connected to the smb registers in any of the headers.
Just purchased the starter kit and freshly installed Simplicity Studio with Simplicity IDE (Not Keil).
Have fallen at the first hurdle...
Studio recognises the starter kit and gives me demo options. If I select Rainbow Blinky, I get an error - "Unable to connect to device 000440088718" during 'Uploading to Device'.
I can't understand why there might be a problem uploading, when it clearly is communicating via the USB port (Win 10 and no reported issues in Device Manager).
Possibly associated problem:
If I go to software examples and select the Blink ASM example, it fails in the CDT Build Console: 'Error: Program "make" not found in PATH'.
In the Project Explorer window, there are frequent declarations of 'No Toolchain...etc').
What is a CDT?
What is a toolchain?