Hot answers tagged

4

The time difference, know as the delta (Δ) is displayed there too. It's 124.6 ns between the markers. The other times you're seeing are the elapsed time from the trigger point. Note that the delta often simply translates to "the difference", so it's not specific to time.


4

It is pointless to try this approach. Synthesis can ONLY read from a file at initialisation time - there are no "files" on an actual FPGA. Reading data in a clocked process requires a hardware interface ranging from a simple serial UART to an Ethernet MAC or a SD card interface (with an SD card socket on your FPGA board), all these re significant projects in ...


3

You need to make nb_Frames_Flash volatile. The compiler sees no change to nb_Frames_Flash anywhere in the code. Thus it implies it is 0. Resulting no code will be inserted for the assignement of CAN_nb_Frames_Tx_cc. (check the assembler, it will be missing) __attribute__((__section__(".nb_Frames"))) volatile const uint32_t nb_Frames_Flash; The volatile ...


3

Just by looking at those lines of code, I think the error might occur in your casting code: //SCALE AND CAST buffer->humidity = (double)(temp_humidity * 100 / (pow(2,14) - 1)); buffer->temperature = (double)(temp_temperature / (pow(2, 14) - 1) * 165 - 40); As you do it, the values get casted after the scaling calculations are done, right before ...


2

Every (relatively recent) MCU (OTP and erasable) I've seen has at least an optional lock bit that prevents reading the memory. The information does not seem to be in the datasheet, so it's probably in another Holtek document. Assuming they had such functionality (and even if they didn't and there was any chance of competitors reverse-engineering) it would be ...


1

To read its content at the given address... I suspect your code has been reduced a bit too much, it is not looking at all like a CPU interface. This might be a school assignment so I only provide an outline of the code. (Which, by the way, has not been syntax checked) ... input [7:0] read_only; ... reg [7:0] write_only; reg [7:0] read_write; always @(...


1

As mentioned by Peter, you measuring inputs are all connected to ground. You could do something like this simulate this circuit – Schematic created using CircuitLab This way you measure 660mV when the active LED is draining 20mA. By the way, 33R seems to be quite small, you may wanna doublecheck the effective forward voltage of your LEDs.


1

To add what @Samuel said... Looks like time resolution is 40 ns/div and cursors are >3 div separation on X axis and 4 div x 1V/div on Y axis. Normally rise time is done from 10% to 90% of the steady state and not 10~90% of the ideal output which appears to reduced to 4.6V for some reason. ( source ESR ) Thus I would suggest you consider response time ...


1

Well first of all: You've chosen the wrong chip for the job. If your this paranoid into securing your application code, you should get a chip that: - supports storing crypto codes. (special masking layer is required for this) - supports execution from encrypted memory. (special memory bus required) But at least you can try: Method 1 has most balance between ...


Only top voted, non community-wiki answers of a minimum length are eligible