7 posts / 0 new
Last post
motred
Offline
Last seen:5 years 4 months ago
Expert
加入:2014-01-20 21:48
xtrim cal on P0_6

Hi Dialog,

我正在使用削减晶体oscillators using prodtest. I'm using the command:
prodtest -p 7 xtrim cal P0_6

For the prodtest uart, I've adapted the prod_test_ES5 firmware to use P0_2 and P0_3 at 115200 baud.

When I pass this command to our device, it times out. I've tried debugging the prod_test_ES5 hardware, and it looks like it's getting stuck in wait_high in pulse.s. I assume that it's waiting for a high pulse on the P0_6 pin, but as far as I can tell I'm giving it a square wave with a period of 1s and a duty cycle of 50%. That signal is being fed into P0_6.

I've also confirmed that datareg is 0x50003000 and shift_bit is 0x40 when measure_pulse is called by Clock_Read in xtal_cal.c. I believe those correctly correspond to P0_6.

Is there anything else that I need to do to use P0_6 for xtrim? What could be causing prod_test_ES5 to not see the signal that I'm sending to it?

BB_Dialog
Offline
Last seen:6 months 1 week ago
Staff
加入:2013-12-05 14:44
Hi Motred,

Hi Motred,

I believe you're doing things right, can't see a wrong syntax or so.
Let me check this with the experts.
Expect an answer on come Monday.

Best regards, BB_Dialog.

BB_Dialog
Offline
Last seen:6 months 1 week ago
Staff
加入:2013-12-05 14:44
Hi,

Hi,

some first feedback:

the 500msec pulse high period should be within 500msec +/- 5 ppm or, 500 msec +/- 0.0025 msec (high period) …
If the pulse period accuracy is not good enough, a time-out will happen.
Low period can be much shorter, (minimum appr. 10 msec).

Another question: is there any other feedback visible on the screen?

Best regards, BB_Dialog.

motred
Offline
Last seen:5 years 4 months ago
Expert
加入:2014-01-20 21:48
Thanks for the input. I'll

Thanks for the input. I'll look at my pulse output and check it's accuracy, but I think it's at 2ppm.

The output I get from prod_test is:

[info] Connecting to COM7
[info] COM7 succesfully opened, baud rate 115200
==== Tx ====>
opcode : 0x4080
length : 0x03
Payload : 80 40 03 07 06 00
status = 9

motred
Offline
Last seen:5 years 4 months ago
Expert
加入:2014-01-20 21:48
Hi Dialog,

Hi Dialog,

We got this figured out. It ended up being a hardware error, and prod_test was working just fine. Thanks for your help.

MHv_Dialog
Offline
Last seen:5 days 8 hours ago
Staff
加入:2013-12-06 15:10
Hi,

Hi,

We are happy to hear that you fixed the issue and appreciate that you let us know. Full steam ahead...

drumste
Offline
Last seen:3 years 3 months ago
加入:2015-05-22 14:58
What kind of hardware error

What kind of hardware error was it? Because I'm trying trimming with xtrim cal command of prof test and I have the same output staus=9.