Hello,
great if everything about configuration is clear now.
You can use "SetFilePointer" to jump from port to port *or* you can use DeviceIoControl(..., IOCTL_DIO_GET/SET/CLR_PIN, ...) to address one single IO by one single call.
You will find sample code here: DeviceDriverDoc.
Hello,
can you please tell me the driver version which is working/not working and if the problem is related to efusA9/efusA)R2 or both.
Thanks.
Hello,
please tell me what are your doubts? <port2> is just a placeholder if you would like to continue to configure futher ports. Else skip it. I better had wrote "reg set value UseAsIO hex 0xf8,0x07,<port2>, ..., <portN>". But I thought it was clear in context with Device Driver Doc. (one byte one port)! Sorry.
analog for port 1!
So if you just use port 0 and 1 set "reg set value UseAsIO hex 0xf8,0x07"
Did you test my settings above at all?
Are you detect any issues with our SW?
Hello,
we changed notation for DIO, refer DeviceDriverDoc, because newer boards may have much more IOs than 32. You can still use "dword" notation but with suffix (UseAsIOA (port 0...3), UseAsIOB (port 4...7), ...)
1) Which exact pins are corresponding to GPIO port 0 on A9r2: pins from 3 to 10 of the 66 pins feature connector ?
Pin 3...7 belongs to port0
Pin 8...10 belongs to port1
2) We try to configure 4 pins In and 4 pins Out altenatively, so on WCE register we set
reg open \drivers\builtin\digitalio
reg set value UseAsIO hex 0xf8,0x07,<port2>,...,port<n>
reg set value DataDir hex 0xA8,0x02,<port2>,...,port<n>
reg save
REM
Hope this helps.
PS: switch off unused SPIs because they may use the same pins:
reg open \drivers\builtin\armStoneA9R2\spi2
reg set value Flags dword 4
reg open \drivers\builtin\armStoneA9R2\spi3
reg set value Flags dword 4
reg save
REM
Hello,
We can only provide support for standard versions of the PicoCOMA5.
In this case, the customer's software is used and we do not have access to it. Please clarify with the customer directly.
Thank you for your understanding.
Hello,
debugport is labled with "COM1" (next to touch connector) you are connected to "COM2"!
Dear Vladimir,
we put new BSP which supports also efusA9xr2 into the download. Please test and let us know if everything works fine on your side.
I put also new "kernel update tool" into your custom downlaod. Here (new introduced) FCR driver is terminated before the update. FCR does dynamically check the Flash for consistency.
Sorry i don't step further in the meanwhile.
I am bound on some other urgent projects.
Is this issue still significant for you? I can spend some more time start in KW42/22
Hello,
Which kernel you are using and which OS?
Which file system is installed (FAT or F3S)?
Your application writes data to flash? How many?
Finally, can we reproduce the issue on a SKIT in our office?
>> Any idea how this is possible?
<< Maybe a bug in my SW. Sorry I have to measure and debug to step further.
>> We worked with version 180316 and I see that this version is skipped in the kernel history?
<< You are right. But I found no information about the changes also not im my emails from around 180316.
So we unfortuneatly lost this information.
Yes, sorry but it should be the correct image and the date in serial debug output should be 220818.
No it should be available but under your custom download folder "deroeve", here are all your images since 2016 are available. If you have no access to this folder contact goretzka@fs-net.de.
Hello, you can download new kernel (220818) from you custom download area.
Hope it works now, "core clock" should show 400MHz, head should be reduced.
Yes this helps. My fault. Looks like instalion of dvfc is not sufficient, you need also an updated ceddk.
I will provide you a new custom kernel with dvfc and ceddk and will come back.
As I told DLL must be copied to ffsdisk.
HW Revison on efusA9 must be 1.2 or higher.
I test it on a efusA9 HW Rev1.2 single core and on a efusA9R2 Rev1.0 quad core.
In the serial boot log you should see something like this if the driver is loaded:
...
PWM: Version 1.4, ActiveKey = Drivers\Active\51
EXTRTC: Version 1.2, ActiveKey = Drivers\Active\52
DVFC: Version 1.0, ActiveKey = Drivers\Active\53
PPU: Version 1.1, ActiveKey = Drivers\Active\54
BCS: Version 1.4, ActiveKey = Drivers\Active\55
...
You can also use ndcucfg -> device enum for check if driver is loaded.
Please come back here with the answers then I will do further checks.
Ok, you see ndcucfg is redireced to COM4:
NDCUCFG V 69 started. Platform: efusA9
NDCUCFG Open COM4 at 115200 Baud
CreateFile() failed -> ERROR COM4
Assume COM4 is in use, not installed or does not exist! So redirect "ndcucfg" to COM1 (debug port) and switch off debug output again:
HKLM/System/ndcucfg/port="COM1:". You may use local console if Ethernet and RS232 instance of ndcucfg is not available.
Or erase Registry by bootloder command "R" ..., your kernel V2.4 180316 should use default setting this is COM1:!
So i assume you set "COM4:" elsewhere in your setup procedure?
Reenabel the boot output again, assume there i no valid image in Flash and we stop in EBoot or while load image so that ndcucfg is not available.
Did you reflash already the image?
"Launch image after reboot : no"!
Must be "yes"!
Try to enter "L1" and reboot if this does not work reflash the kernel.
Seems the image is not available any more.
What's the output of enter bootloader command "i"?
