failed on a simple axi-lite rm with partial reconfiguration
hi,

i want to switch the function of adding/subtracting/multiplying in one partition block with partial reconfiguration.

the adder/subtractor ip is generated by hls in the following c-code

void add(int a, int b, int& c) { // <-- may change to different top names

#pragma hls interface ap\_ctrl\_n…
hi , i try it with this scenario, it work.

[[image]](https://aws1.discourse-cdn.com/business5/uploads/pynq1/original/1x/1ef72ed473166fc2811618e9c1ec0febb7a2ecc8.png "image")

test code:

ov1 = overlay(’/home/xilinx/haddsub/prio.bit’)

pr=ov1.pr\_decoupler\_0

pr.write(0x0, 0) <- default set to zero

// before download partial bitstream set to one

pr.write(0x0, 1)

add\_pb=bitstream(’/home/xilinx/haddsub/pr\_0\_sub.bit’, n…
set both sides of the connection to autonegotiate & set both sides of the connection to half duplex & set both sides of the connection to full duplex as long as you write down the hierarchy manually, there’s certainly the possibility to simplify such transitive from implementations with a macro. [i’ve written one here, feel free to take a look.](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=337cce675aa28e99ac030ca783c1c155) going even further one could try to use procedural macros with global state that uses annotations on the… in this case you need to use a feature in airtable api called filter by formula. the blocks you did will not work. yes, you can using a module.

you might have seen examples of module where a only a symbol is given, e.g. from the docs:

data = mx.sym.variable('data')

fc1 = mx.sym.fullyconnected(data, name='fc1', num\_hidden=128)

act1 = mx.sym.activation(fc1, name='relu1', act\_type="relu")

fc2 = mx.sym.fullyconn… check out the intersect function.
here is one approach:
% generate a rectangular boundry
rectx = [0.1 0.1 0.9 0.9];
recty = [0.1 0.5 0.5 0.1];
rect = polyshape(rectx,recty);

% initialize a figure for display purposes
figure(1);clf
titles = [...
 "all lines";...
 "partially within";...
 "exclusively within"];
for i = 1:3
 subplot(1,3,i)
 hold on
 title(titles(i))
 plot(rect)
 xlim([0 1])
 ylim([0 1])
end

% define the number of line segments to generate
nlines = 25;

% initialize a structure to store the lines (if you need the data later)
lines = struct();

% generate each line, calculate it's intersection conditions, and plot
for i=1:nlines
 
 % generate points for a random line segment
 lines(i).points = rand(2);
 
 % section the line into parts at intersection with the rectangle
 [in, out] = intersect(rect, lines(i).points);
 
 % plot all the lines that were generated
 subplot(1,3,1)
 line(lines(i).points(:,1),lines(i).points(:,2))
 
 % plot lines that are partially within the boundary
 if isempty(in)==0
 subplot(1,3,2)
 line(lines(i).points(:,1),lines(i).points(:,2))
 end
 
 % plot lines that are exclusively within the boundary
 if isempty(out)==1
 subplot(1,3,3)
 line(lines(i).points(:,1),lines(i).points(:,2))
 end
end
here is the output: Magda, have you found what you need, yet?


I did this many years ago. It is simple… the 2nd time you do it!  

Exit points are simply “interrupts” that IBM supplies. You can attach programs to them, and the programs will automatically run at that point. For setting your AS/400 up to accept FTP logons, for example, the exit point is:  

QIBM\_QTMF\_SVR\_LOGON and the format you wil use is: TCPL0100.


A program inserted there can control WHO can log on, and when.  

To control WHAT they can do, you use another exit point, QIBM\_QTMF\_SERVER\_REQ and use format VLRQ0100.


My notes (from 1999) say I used the IBM TCP manual to get this info, specifically: TCP/IP manual SC41-5420-01 page I-14.


I do not know if it will allow me to post code here, it is long and complex due to the number of variables and some of them being in hex.


Write me (drow@waxie.com) if you would like me to email you my program code.


David Row  

WAXIE Sanitary Supply  

San Diego, CA





This is a link for [Add-ons for Firefox](https://addons.mozilla.org/en-US/firefox/). These are programs written by users or developers that the browser knows how and when to call. The developers of Firefox designed it to allow external programs to be hooked in by users of the browser.


IBM did something similar for a lot of the TCP/IP and other server functions. (And a lot of other things.) When you connect to the FTP server for example, the server checks to see if a program has been registered to process FTP logon requests. The registered program is an ‘exit program’.


Browser add-ons get an entry added to a file someplace within the browser directory structure. In your iSeries, the entry would be added to the Registration Facility. (Not always, but that’s the commonly recognized object for exit points and programs.) Use WRKREGINF to review your registration facility.


To create an exit program, you need to know the parameter list that will be passed to your program and the exit protocol. To find the parameter list, you should start looking at the documentation for the server the exit program will be associated with. The protocol, the meanings of the parms and what to with them, is also there.


A FTP exit program would be structured after documentation within the [File Transfer Protocol exit programs](http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaiq/rzaiqreferenceexit.htm) topic of the Information Center for your release.


Once registered, a server logon exit program (for example) would be called just before the server decides whether or not to accept the logon. Your exit program directly influences that decision by returning an ‘accept or reject’ parameter. It chooses based on examination of the input parms.


The exit program may control who can and cannot logon, where they may logon from, what times of day logons are accepted, or it might accept all logons — its purpose can be simply to write all logons to a log file or to send a message when particular logons happen. Your exit program can do whatever it is programmed to do at that point in the logon process.


It doesn’t have to be a ‘security’ function. It’s whatever you want it to be.


For the FTP server, there are two general exit points. One is just before a logon is accepted. The other is just before each transaction in a session is processed. You can control individual transactions just as you can logons. (FTP client has its own exit points.)


Most other exit programs work on similar principles.


A few issues complicate things.


* An exit program needs enough authority to do whatever it needs to do; it can’t always rely on the authority of the session user.
* An exit program shouldn’t unduly delay transactions; there’s no way to know how often an exit program may be called, so you don’t want it slowing down every single transaction.
* Exit programs may be called by many instances of a server at the same time; it shouldn’t be locking things that are needed by a different instance.
* IBM changes the interfaces at times and the servers themselves can get PTFs; regular, on-going maintenance can be needed — keep the programs direct with little complication.
* There are other issues, but those are enough to consider.


Code a very simple exit program that accepts the parms and returns an ‘Accept’ indication. Don’t have it do anything except maybe send a message to a message queue. That lets you see how the registration facility works and how the parms work. It also gives you a program that you can register and deregister in the future to check whether or not the server is stilling calling your program correctly. (Problems can happen.)


Tom see above to learn how to setup and configure ip passthrough mode for your router. if you need further assistance with your ip passthrough setup and configuration contact connectech support. jared, at&t community specialist hi there,

i am making some assumptions about the requirements of your experiment here but lets see if this helps.

short break

would you like the short break to be at the start of each trial ? i.e. the inter-trial-interval? if so try the following:

add a code component to your “trial” routine (c… not [full disclosure] a linux person per se.

something similar to the following should work:

https://www.unix.com/shell-programming-and-scripting/68166-converting-integer-string.html

start simple with just enough code to test the concept.

see if it works and modify/correct as necessary.

then if it still does not work, then post your documented code accordingly along an explanation of what is or is not happening as you expect or desire. the compiler will throw the following errors:  


10: error: increment of read-only variable **k**,  


12: error: **lvalue** required as increment operand.